Rework physics versions used in our System tests (least clm4_5, midlevel clm5_0, and most clm6_0)

[ekluzek]

With #2378 coming in we need to look at our test lists and revamp them in view of the CESM3 release. Mainly I think most tests should be clm6_0, but some still for clm5_0 and clm4_5.

With #2379 we also should have minimal testing for clm5_1. But, we can only completely remove it when CAM and CESM have moved to remove clm5_1 in their compsets.

Maybe it's time to drop some of the clm4_5 testing with a new physics version available? I think the testing should scale up from clm4_5 with more for clm5_0 and then the most for clm6_0.

[ekluzek]

There are also some long standing testing issues that could be addressed with this:

#47
#275
#615
#1186
#1242
#1341
#1584
#1859
#2078
#2151

[ekluzek]

This came up because I'm working on #2378 and I'll need to do something with clm5_1 and clm6_0 testing for it. From scoping this out, I think this is more important to do some careful thinking about and designing what we want it to look like. So I'll make this a post CTSM5.2 issue.

[ekluzek]

Another complexity is that we need to add a LND_TUNING_MODE for clm6_0_cam7.0. And the same way that we should do most testing for clm6_0, we should do the most for clm6_0_cam7.0 LND_TUNING_MODE.

[ekluzek]

It looks like the only testing that CAM and CESM have with clm5_1 are for the ne30np4.pg3 grid for SMS and ERP, on derecho with debug. So the clm5_1 testing can be very limited.

[samsrabin]

I will create a Project called "Revamp testing in preparation for the CESM3 release" with this and other issues in it.

[samsrabin]

Added Project 30.

@ekluzek Do you want to change access permissions so that anyone can view it? I don't have permissions to do that (even though I'm an admin of the project, which is annoying).

It might also be good to rename this issue to something more specific, like "Rework CTSM versions used in tests."

[ekluzek]

@samsrabin thanks for pointing that out. Since this is ESCOMP level I've asked @billsacks to update the privacy level of the project board. Only ESCOMP admin's can do that.