add override capabilities to repeated capabilities documentation

[elebel-emerson]

• This contribution adheres to CONTRIBUTING.md.

- [ ] I've updated CHANGELOG.md if applicable.

• I've added tests applicable for this pull request

What does this Pull Request accomplish?

Change generated Repeated Capabilities documentation to support metadata-defined descriptions, examples, and identifier guidance for capability-specific behavior.

What testing has been done?

Manually testing change in config.py propagates to html documentation
Create a unit test

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.26%. Comparing base (ab52ec6) to head (33883f0).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2183      +/-   ##
==========================================
- Coverage   89.85%   89.26%   -0.59%     
==========================================
  Files          73       71       -2     
  Lines       19006    18765     -241     
==========================================
- Hits        17077    16751     -326     
- Misses       1929     2014      +85     

Flag	Coverage Δ
codegenunittests	84.98% <100.00%> (+0.08%)	⬆️
nidcpowersystemtests	94.38% <ø> (-0.23%)	⬇️
nidcpowerunittests	89.53% <ø> (ø)
nidigitalsystemtests	92.02% <ø> (-0.24%)	⬇️
nidigitalunittests	68.44% <ø> (ø)
nidmmsystemtests	92.29% <ø> (-0.44%)	⬇️
nifakeunittests	86.04% <100.00%> (+0.03%)	⬆️
nifgensystemtests	94.32% <ø> (-0.30%)	⬇️
nimodinstsystemtests	73.85% <ø> (ø)
nimodinstunittests	94.20% <ø> (ø)
nirfsgsystemtests	81.12% <ø> (ø)
niscopesystemtests	89.96% <ø> (-2.99%)	⬇️
niscopeunittests	43.20% <ø> (ø)
nisesystemtests	91.50% <ø> (ø)
niswitchsystemtests	81.56% <ø> (-0.48%)	⬇️
nitclksystemtests	?
nitclkunittests	98.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
build/helper/metadata_add_all.py	81.48% <100.00%> (+0.38%)	⬆️
generated/nifake/nifake/_converters.py	95.74% <100.00%> (+0.09%)	⬆️

... and 13 files with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ab52ec6...33883f0. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ni-jfitzger]

Why are you changing the file modes of our metadata files?

[ni-jfitzger]

Note: if you pull the latest changes, the system tests will pass.
Not really a requirement for this change, but the PR Checks would look better.

[elebel-emerson]

Why are you changing the file modes of our metadata files?

I did not explicitly touch those files, doing tox -e codegen touched those files, and I just committed.
Removed the changed to file mode in 92b5d19

[elebel-emerson]

Note: if you pull the latest changes, the system tests will pass. Not really a requirement for this change, but the PR Checks would look better.

git pull origin says I am up to date with origin. Still one failing change that does not seem correlated to this change

[ni-jfitzger]

Note: if you pull the latest changes, the system tests will pass. Not really a requirement for this change, but the PR Checks would look better.

git pull origin says I am up to date with origin. Still one failing change that does not seem correlated to this change

Yeah, any system test failures are unrelated to your changes. You haven't touched the API or the System Tests.

[marcoskirsch]

"overwrite" should be "override" (nim-python terminology)

[marcoskirsch]

You are missing a NI-FAKE example

[elebel-emerson]

"overwrite" should be "override" (nim-python terminology)

Hopefully changed all instances of "overwrite" to "override"

You are missing a NI-FAKE example

Added unit tests in test_rep_caps_template.py

[ni-jfitzger]

Your changes to metadata_add_all.py are causing related unit tests to fail.