Ensure CNM-S collection name is compatible with GIBS

[ckhowardASDC]

Some DAACs use slashes (/) in their UMM-Var (e.g. product/vertical_column). bignbit appends that variable to the collection name, and you get something like TEMPO_HCHO_L3_V04_product/vertical_column. GIBS does not support slashes in collection names.

We tried to rename the UMM-Var so this wouldn't be an issue but unfortunately some of the services in Harmony look for the specific UMM-Var within the data file, if the UMM-Var gets changed, the service looks for a group/variable in the data file that does not exist.

bignbit may have to remove slashes from CNM-S collection names, or GIBS may have to add support for collections with slashes.

This is currently a blocker for TEMPO Browse.

[frankinspace]

Easy fix on the bignbit side would be a replace '/' with '_' (or another valid char) here:
https://github.com/podaac/bignbit/blob/develop/bignbit/send_to_gitc.py#L135

[frankinspace]

The GIBS ICD "Table 5.3-1 CNM Message Properties – Validation Requirements" does not actually specify any limitations on the collection name other than it needs to be a "Text String (No Spaces)"
https://wiki.earthdata.nasa.gov/download/attachments/176426242/GIBS_-_Imagery_Provider_ICD%28RevB_Final%29.pdf?version=1&modificationDate=1681735056555&api=v2

This really should be updated to reflect the constraints if this is an intentional limitation of the GIBS interface.