Fluxsite configurations should be accessible as standalone configurations for CABLE

[SeanBryan51]

There is a need to have accessible run configurations for site based runs in the CABLE community. Instead of building up the fluxsite run configurations by hand within benchcab, we should make these configurations accessible elsewhere and base benchcab model runs off these configurations.

[Related conversation from slack 07/05/24]

Sean: We could probably pull out the namelist files from the bench_example repo and put these in a configuration specific to site runs? We could use this configuration as a basis for all the site runs in benchcab (instead of having a configuration for each site met forcing).

Claire: Yes, I would not copy for each site met forcing. But I think we would need a different namelist/configuration per science configuration. That’s from what Gab said.
We probably also can clean up the namelist file: it probably has plenty of options listed which are not used.
Maybe we could try and have the namelist files as clean as possible in supported configurations: only the options that are actually needed are listed.

[ccarouge]

This is linked to the conversation on how to organise configurations for CABLE in general: CABLE-LSM/CABLE#284