Add maxLength validation keywords matching nvarchar values in archive_catalog

[braingram]

Closes spacetelescope/roman_datamodels#342

Add maxLength validation keywords matching nvarchar values in archive_catalog portions of the schemas. A few cases were not handled:

• nvarchar(max) as max is undetermined
• nvarchar datatype for non-string values. I don't see any way to enforce these as the thing being validated is not a string. Examples are:
  • rotation_matrix in mosaic_wcs_info
  • read_pattern in exposure

The TVAC and FPS schemas are not updated by this PR.

A test was added to check that these match which walks the schemas looking for archive_catalog and if it contains a nvarchar (that isn't max) and if the subschema has type: string the test checks the subschema has a maxLength keyword and that it's value matches the one in nvarchar. As this PR fixes the schemas no errors are seen in the CI but some examples of errors are:

• For a missing maxLength: AssertionError: archive_catalog has nvarchar, schema asdf://stsci.edu/datamodels/roman/schemas/aperture-1.0.0 is missing maxLength
• For a mismatch: AssertionError: archive_catalog nvarchar does not match maxLength in schema asdf://stsci.edu/datamodels/roman/schemas/aperture-1.0.0

Regression tests running with this PR and roman_datamodels dev (to pick up changes in spacetelescope/roman_datamodels#388):
https://github.com/spacetelescope/RegressionTests/actions/runs/11060303121

Prior to merging this PR I think it makes sense to set the romancal required version for rad and roman_datamodels to dev (so that subsequent work on rad and roman_datamodels can be tested).

Tasks

• Update or add relevant rad tests.
• Update relevant docstrings and / or docs/ page.
• Does this PR change any schema files?
  • Schema changes were discussed at RAD Review Board meeting.
• Does this PR change any API used downstream? (If not, label with no-changelog-entry-needed.)
  • Write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see below for change types).
  • Start a romancal regression test (https://github.com/spacetelescope/RegressionTests/actions/workflows/romancal.yml) with this branch installed ("git+https://github.com/<fork>/rad@<branch>").
  • Update relevant roman_datamodels utilities and tests.

News fragment change types:

• changes/<PR#>.feature.rst: new feature
• changes/<PR#>.bugfix.rst: fixes an issue
• changes/<PR#>.doc.rst: documentation change
• changes/<PR#>.removal.rst: deprecation or removal of public API
• changes/<PR#>.misc.rst: infrastructure or miscellaneous change

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.81%. Comparing base (f6c4abc) to head (057bf92).
Report is 166 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #448      +/-   ##
==========================================
+ Coverage   95.45%   95.81%   +0.35%     
==========================================
  Files           4        4              
  Lines         198      215      +17     
==========================================
+ Hits          189      206      +17     
  Misses          9        9              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[schlafly]

Thanks Brett. That's great. I had forgotten the read_pattern and rotation_matrix cases. I think you're right to ignore these as those lengths were picked to be very large and it's hard to see how they will cause problems. It's also good not to touch TVAC & FPS.

[PaulHuwe]

Agreed on pointing to dev for tickets (other PRs will need it as well).