As a user, I want to validate a bundle with collections having different label extensions

[jordanpadams]

💪 Motivation

...so that I can validate intermingled lblx/xml bundles

📖 Additional Details

• CCB-260.pdf
• Follow-on to #482 this builds on that support to enable intermingled LBLX/XML at the collection level
• for example:

bundle
|-- collection_x (XML)
|-- collection_y (LBLX)
|-- collection_z (XML)

⚖️ Acceptance Criteria

Given When I perform Then I expect

⚙️ Engineering Details

• [ ] create 1 new flags to specify exception to the label extension specified 2. specify label file extension exception path --extension-exception-paths /path/to/collection1 /path/to/collection2, which specifies the relative path from bundle root where a collection will use a different extension than what is specified by --extension. NOTE: this is only allowed when -R pds4.bundle is executed.
• [ ] if xml, crawl for .xml files, validate that there are no files with .lblx suffix (it is now a reserved extension)
• [ ] if lblx, crawl for .lblx files,
• [ ] if --extension-exception-path specified, those paths should contain the opposite extension of --extension

Example per example bundle above

# Crawl bundle, validate LBLX labels, except XML in /path/to/collection1
validate -R pds4.bundle /path/to/bundle.xml --extension xml --extension-exception-paths /path/to/collection_y

# or equivalently
validate -R pds4.bundle /path/to/bundle.lblx --extension lblx --extension-exception-paths collection_x/ collection_z/