Allow tests to use different mpas_analysis environment

[forsyth2]

Summary

Objectives:

• Add the ability to specify environment_commands for mpas_analysis in testing. (Note this was always possible as a user: just set environment_commands in the cfg).

Issue resolution:

• Allows for testing of Add additional files to the mpas-analysis cache for time series analysis #760.

Select one: This pull request is...

• a bug fix: increment the patch version
• a small improvement: increment the minor version
• a new feature: increment the minor version
• an incompatible (non-backwards compatible) API change: increment the major version

Small Change

• To merge, I will use "Squash and merge". That is, this change should be a single commit.
• Logic: I have visually inspected the entire pull request myself.
• Pre-commit checks: All the pre-commits checks have passed.

[forsyth2]

@chengzhuzhang I think this should be fine to merge.

A couple notes:

• The bundle cfgs weren't updated because they don't have a mpas_analysis task set up.
• I did update the legacy cfgs, which we normally think of as "frozen", but the change is the value of environment_commands, not the parameters themselves. So, it's really no different than, for example, running the latest e3sm_diags dev environment on a legacy cfg.

[chengzhuzhang]

okay, I thought specifying environment_commands was already enabled. This PR is just for testing. If it is the case, perhaps to update the title to avoid confusion.

[forsyth2]

I thought specifying environment_commands was already enabled.

Yes, sorry, I tried to clear that up in the PR description. This is exclusively for auto-generating the test cfgs.

perhaps to update the title to avoid confusion.

Good idea; I've updated it to "Allow tests to use different mpas_analysis environment".

[forsyth2]

These are sort-of meta-environment commands -- i.e., <task_name>_environment_commands is really saying "what should we set as environment_commands in each of the auto-generated test cfgs for task <task_name>?"

[forsyth2]

That's also why nothing changes in default.ini, which is where a user-facing parameter change would go.

[forsyth2]

I'm going to hold off on merging this until we get a passing test of #760. Based on #760 (comment), it makes sense to add a conditional change to the mapMpiTasks used in testing based on the environment chosen.

[forsyth2]

Now that #760 has merged, I'm also going to merge this testing fix.