Back merge fixes for release candidate/1.7.0

[tloubrieu-jpl]

🗒️ Summary

Back merge changes made while preparing for the release 1.7.0 deployment in production with terraform.
Introduced more flexibility in the integration testing to use different registry branches and local registry-api docker tags.

🤖 AI Assistance Disclosure

• No AI assistance used
• AI used for light assistance (e.g., suggestions, refactoring, documentation help, minor edits)
• AI used for moderate content generation (AI generated some code or logic, but the developer authored or heavily revised the majority)
• AI generated substantial portions of this code

Estimated % of code influenced by AI: 90 %

⚙️ Test Data and/or Report

Tested with the integration tests automated on the branch as well as terraform deployment with integration tests in the AWS Test venue.

♻️ Related Issues

Fixes NASA-PDS/registry#542

🤓 Reviewer Checklist

Reviewers: Please verify the following before approving this pull request.

Documentation and PR Content

• Documentation: README, Wiki, or inline documentation (Sphinx, Javadoc, Docstrings) have been updated to reflect these changes.
• Issue Traceability: The PR is linked to a valid GitHub Issue
• PR Title: The PR title is "user-friendly" clearly identifying what is being fixed or the new feature being added, that if you saw it in the Release Notes for a tool, you would be able to get the gist of what was done.

Security & Quality

• SonarCloud: Confirmed no new High or Critical security findings.
• Secrets Detection: Verified that the Secrets Detection scan passed and no sensitive information (keys, tokens, PII) is exposed.
• Code Quality: Code follows organization style guidelines and best practices for the specific language (e.g., PEP 8, Google Java Style).

Testing & Validation

• Test Accuracy: Verified that test data is accurate, representative of real-world PDS4 scenarios, and sufficient for the logic being tested.
• Coverage: Automated tests cover new logic and edge cases.
• Local Verification: (If applicable) Successfully built and ran the changes in a local or staging environment.

Maintenance

• Backward Compatibility: Confirmed that these changes do not break existing downstream dependencies or API contracts (or that breaking changes are clearly documented).

Terraform (only if this PR touches a terraform/ directory)

• Validator run: scripts/validate_terraform.py was run against the changed terraform/ tree and any Must-Have failures were resolved (or are tracked in a reviewed .tfvalidate-ignore entry, not silently bypassed).
• Ownership boundary: Shared/singleton CDS resources (Cognito, CloudFront, org-wide IAM roles, shared security groups) were only added/changed in pdc-cds-infra, not duplicated in an application repo.
• Module structure: modules/ stays flat and no new module is just a thin wrapper around a single resource.
• SSM interface: Any new cross-component output is actually published under /pds/<component>/... and, if this PR is the consumer side, reads from the correct published parameter rather than another repo's Terraform state.
• Naming intent: Resource and variable names are semantically meaningful, not just non-redundant (the validator only checks for repeated resource-type substrings).
• Auth at runtime: Terraform/CI actually authenticates via OIDC or an assumed role when applied — not just "no static key found in this diff."
• Least privilege: Any new or changed IAM policy attached to the Terraform execution role grants only what this change needs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jordanpadams]

@tloubrieu-jpl similar to the discussion on sweepers, I will merge #813 and then merge main back into develop