Add -c flag to registry-manager to align CLI with harvest

[jordanpadams]

🗒️ Summary

Adds a -c <harvest-config.xml> flag to registry-manager so operators can use the same Harvest configuration XML they already maintain, instead of passing the registry connection URL and auth file as separate -registry and -auth flags.

Changes:

• New HarvestConfigReader utility parses the <registry auth="...">url</registry> element from a Harvest config XML
• CliCommand.getConfigPair() resolves connection info from either -c (preferred) or -registry/-auth (deprecated)
• -registry and -auth remain functional but emit a [WARN] deprecation message at runtime
• Hard-coded null check on -auth in list-dd removed — no longer needed when auth comes from -c
• All 14 sub-commands updated to use getConfigPair()
• Updated printHelp() and checkVersion() in RegistryManagerCli

Before:

registry-manager delete-data -registry file:///path/to/config.xml -auth /path/to/auth.txt -lidvid ...

After:

registry-manager delete-data -c /path/to/harvest-config.xml -lidvid ...

🤖 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

Build verified with mvn clean install -DskipTests -pl manager -am and mvn clean install -DskipTests -pl harvest -am — both pass. Manual end-to-end test against a live OpenSearch instance pending (requires real config file).

♻️ Related Issues

Fixes #62

🤓 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).

[tloubrieu-jpl]

I agree registry-manager and harvest integration needs improvement to help the users, but I am not too sure what the -c integration means since the registry manager uses a per connection configuration, whereas harvest configuration is a per job configuration (e.g. dataset to upload) which contains the connection parameter.

I guess that works as a pragmatic change for users to re-use their current harvest config when deleting data for example, but that sound a bit confusin for me.

[jordanpadams]

@tloubrieu-jpl I think the configs need to be more clearly described as to what is what, but all of the necessary information is already in the harvest configuration. I am hoping to rebrand that as a "registry configuration" and supports all registry-related tools (harvest, registry-mgr, registry-client). So some configuration applies to some tools, some apply to others, but they need one config file.

having to run all of these tools with different configs seems very confusing and a bit painful from a user experience perspective. I only run these tools once in a while, but I forget what config and values are used for what every time I run each tool and get it wrong 50% of the time.

[jordanpadams]

Open to other ideas! But I think some consolidation of some kind should happen if we can.

[jordanpadams]

Note: Waiting to merge this PR until integration tests are working so we can verify this change is backwards compatible.

[sonarqubecloud]

Quality Gate failed

Failed conditions
9.1% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud