Cam sima dycore update

[PeterHjortLauritzen]

Tag name (required for release branches):
Originator(s):

Description (include the issue title, and the keyword ['closes', 'fixes', 'resolves'] followed by the issue number):

This PR should enable the use of the SE dycore with the CAM4 physics suite.

Describe any changes made to build system:

Describe any changes made to the namelist:

List any changes to the defaults for the input datasets (e.g. boundary datasets):

List all files eliminated and why:

List all files added and what they do:

List all existing files that have been modified, and describe the changes:
(Helpful git command: git diff --name-status development...<your_branch_name>)

If there are new failures (compared to the test/existing-test-failures.txt file),
have them OK'd by the gatekeeper, note them here, and add them to the file.
If there are baseline differences, include the test and the reason for the
diff. What is the nature of the change? Roundoff?

derecho/intel/aux_sima:

derecho/gnu/aux_sima:

If this changes climate describe any run(s) done to evaluate the new
climate in enough detail that it(they) could be reproduced:

CAM-SIMA date used for the baseline comparison tests if different than latest:

[jimmielin]

Thanks @PeterHjortLauritzen! Some early comments.

I think there are a handful of instances in the dycore that have code walled off using #ifdef 0 and a comment, for much of the code that depends on tracers/chemistry/constituents and history, which were previously unsupported. Not sure if we should begin to implement these now or continue to wall these off (perhaps in a constituent manner to what is there now, i.e., change all to #ifdef 0) so they can be dealt with together at a later time.

[jimmielin]

Note -- maybe it could be addressed in this PR: To support CAM7 moving mountain gravity waves the vort4gw code needs to be ported from CAM to the SE dycore code here as well (instead of using the pbuf just populate vorticity in physics_state so it is visible to the CCPP schemes via the CAM-SIMA registry)

[PeterHjortLauritzen]

FYI: In FKESSLER (10 day test) solution is B4B with cam_development tag cam6_4_089 when performance enhacement PR has been committed (ESCOMP/CAM#1365)

[jimmielin]

Thanks @PeterHjortLauritzen!

Since this is bit-for-bit with cam_development and I have no further questions about the code I'll approve it from my end! Depending on whether this or the gravity waves PR goes in first I'm happy to handle whatever merge conflicts arise due to vorticity code updates in the GW PR that also affect the SE dycore.