Implement SIP generation offline capabilities

[jordanpadams]

Formal requirements to come (#3), but for now, we need to get something together to accomplish this.

Informal requirements:

1. Software shall produce SIP Manifest table (and eventually AIP manifest (Implement SIP generation offline capabilities #2)) with accompanying label
2. The SIP Manifest should be a tab-separated 4 column manifest table with columns, checksum, checksum_type, file_specification_url, LIDVID (see example ladee_mission_bundle_SIP_4col_manifest_v1.0.xml and ladee_mission_bundle_SIP_4col_manifest_v1.0.tab in attached .zip)
3. A user will input a bundle directory, and the software will read the bundle.xml at the top level of the bundle. The software then proceed to query the registry for all primary products associated with that bundle (using the bundle lidvid) (not sure if this is possible, if not. we may need to parse all the collection lidvids/lids from the bundle.xml and use those to query the registry).
4. From the registry output, we should parse the necessary fields to populate the SIP Manifest.
5. More to come...

Use https://pds-dev-el7.jpl.nasa.gov/services/registry/pds/select?q=*%3A* for testing.

Example Python implementation, SIP/AIP products, templates, etc: aaaZip_NSSDC_20190820.zip
Test bundle: https://atmos.nmsu.edu/PDS/data/PDS4/LADEE/mission_bundle/ (fixed URL)

Applicable requirements
Primary - 🦄 #48
Secondary - 🦄 #49 🦄 #45 🦄 #46