Add supersede / update product version functionality in Registry Manager

[tdddblog]

🗒️ Summary

Add supersede / update product version functionality in Registry Manager

⚙️ Test Data and/or Report

Build the projects
(1) Build and install "registry-common" jar first (see NASA-PDS/registry-common#24)
(2) Build registry manager

Test

• Ingest two documents (also attached to Re-imagine Registry Handling of Product Versioning registry#55)
  (1) https://pds.nasa.gov/data/pds4/context-pds4/instrument/vg1.crs_1.0_deprecated.xml
  (2) https://pds.nasa.gov/data/pds4/context-pds4/instrument/vg1.crs_1.0.xml

• Create a CSV file with one row and 2 columns (old and new LIDVIDs):

urn:nasa:pds:context:instrument:crs.vg1::1.0,urn:nasa:pds:context:instrument:vg1.crs::1.0

• Run registry manager's new "update-alt-ids" command. Pass a file path of the CSV file:

registry-manager update-alt-ids -file /tmp/alt-ids.csv

• Check OpenSearch index. Both urn:nasa:pds:context:instrument:crs.vg1::1.0 and urn:nasa:pds:context:instrument:vg1.crs::1.0 documents should have following "alternative_ids" values:

["urn:nasa:pds:context:instrument:crs.vg1",
"urn:nasa:pds:context:instrument:crs.vg1::1.0",
"urn:nasa:pds:context:instrument:vg1.crs",
"urn:nasa:pds:context:instrument:vg1.crs::1.0"]

♻️ Related Issues

NASA-PDS/registry#56
NASA-PDS/registry#59

NASA-PDS/registry-api#426
NASA-PDS/registry-api#427