A summary of CDDS-related issues

Nobody has claimed this yet.

This issue contains a summary of issues related to CDDS, to remind us to discuss them with the CDDS team 😊

1. #153: Would it be possible to update the `GCModelDev` CVs so we can specify a bespoke license for CMEW, please?
2. Following on from #154: Would is be possible to integrate `~hadmm/CDDS/github/ceda-mip-tools` into CDDS, please? (We are now using this directly in CMEW.)
3. #128: Would it be possible to ensure that messages from CDDS are not sent to `job.err` unless there is an error, please?
4. Would it be possible to add to the CDDS documentation details about pre-requisites for running CDDS, e.g. needing a MASS / moose account, please?
5. Are there any major differences to the `GCModelDev` MIP tables compared to the `CMIP6` MIP tables? Or is it just the CVs that are different?
6. Would it be possible to write the file paths created by `create_cdds_directory_structure` to somewhere accessible so that it can be picked up by another task? The context here is that we want to remove the extracted pp files in a housekeeping task, #30

Start by reviewing linked issues #153, #154, #128, and #30, then separate the remaining CDDS requests in this summary. Check the CDDS documentation and the workflow entry points mentioned, including create_cdds_directory_structure. Done would require agreeing which individual request is being undertaken and defining its acceptance criteria.

Written by the indexing model from the issue text.