Add suite creation and jedi config render tests

[mranst]

This PR adds two code tests discussed in #736. The first simply creates all suites to ensure they are configured correctly, and do not contain defer_to_platform or defer_to_model.

The second test renders the jedi config yaml for all JEDI suites and evaluates differences to a set of stored files. These are constructed in a dry-run mode, where observations are not fetched and all filepath prefixes are replaced by placeholders. The idea behind this test is to ensure all configs are able to be successfully constructed, and also can be used to evaluate changes to jedi configs, as any change will be reflected in the file diff as part of a PR. Any change to a jedi yaml is expected to trigger a failure in this test. To make it easy to account for changes, I have introduced a script that can be run using swell utility CreateMockConfigs that will automatically regenerate all of the configs used for comparison in the source code.

I have implemented these tests as part of the regular code testing, as they add only about 20 seconds to the runtime of the code tests, but we can potentially look at implementing them in a different way, such as part of a new workflow

[mer-a-o]

@mranst I'm testing this branch, I'm getting this:
SwellCreateExperiment: Creating experiment: 'swell-ufo_testing' in '/gpfsm/dnb33/tdirs/login/discover36.174920.mabdiosk/tmpeqil1jlx' in the output. I also see directories and files generated in test_cache_location: /discover/nobackup/mabdiosk/SwellExperiments/swell-test-cache which is iset in my ~/.swell/swell-test.yaml

[mranst]

@mranst I'm testing this branch, I'm getting this: SwellCreateExperiment: Creating experiment: 'swell-ufo_testing' in '/gpfsm/dnb33/tdirs/login/discover36.174920.mabdiosk/tmpeqil1jlx' in the output. I also see directories and files generated in test_cache_location: /discover/nobackup/mabdiosk/SwellExperiments/swell-test-cache which is iset in my ~/.swell/swell-test.yaml

Thanks, they should both now go to the test cache

[mer-a-o]

It's working correctly now. Thanks @mranst !