As a user, I would like to provide a custom base manifest URL

[smclaughlin7]

Add a testing mode to the pds-deep-archive software that lets the user (a node) specify the <manifest_url> location to use in the resulting SIP product label.

💪 Motivation

For some new archives, such as the Catalina Sky Survey that accumulates data into new collection versions on a nightly basis and delivers to the NSSDCA every week, the delivering node, the NSSDCA, and most likely EN will need to perform end-to-end testing before deliveries to the NSSDCA go live.

Presently pds-deep-archive hardcodes <manifest_url> in the SIP label to point to the manifest repository at EN, https://pds.nasa.gov/data/pds4/manifests/2021/. However for many of these end-to-end tests each SIP product will reside locally online at the node. This requires the NSSDCA to manually edit each SIP label and change <manifest_url> to point to the SIP manifest location at the node.

📖 Additional Details

None

⚖️ Acceptance Criteria

Given a test mode is added to pds-deep-archive,
when I run pds-deep-archive for an end-to-end test
then I expect the software to let me specifiy or input the SIP <manifest_url> location that will override the hardcoded URL to EN's manifest repository.

⚙️ Engineering Details

[jordanpadams]

thanks @smclaughlin7 we will add this to the queue