[Release-v2.1.0] Updated comprehensive tests to include WoFS tests for E2E testing

[mark-a-potts]

DESCRIPTION OF CHANGES:

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

TESTS CONDUCTED:

• hera.intel
• orion.intel
• cheyenne.intel
• cheyenne.gnu
• gaea.intel
• jet.intel
• wcoss2.intel
• NOAA Cloud (indicate which platform)
• Jenkins
• fundamental test suite
• comprehensive tests (specify which if a subset was used)

LABELS (optional):

A Code Manager needs to add the following labels to this PR:

• Work In Progress
• bug
• enhancement
• documentation
• release
• high priority
• run_ci
• run_we2e_fundamental_tests
• run_we2e_comprehensive_tests
• Needs Cheyenne test
• Needs Jet test
• Needs Hera test
• Needs Orion test
• help wanted

[MichaelLueken]

This update adds two WoFS tests to the comprehensive E2E tests. Approving and adding run_we2e_comprehensive_tests label to the PR. Please note that the Orion Jenkins CI might not work until Orion has returned from maintenance.

[MichaelLueken]

@mark-a-potts @jessemcfarland The run_we2e_comprehensive_tests label isn't kicking off the Jenkins CI tests. Is this label setup on the Jenkins side? Should I use the run_we2e_fundamental_tests, stop the job in Jenkins, then set the SRW_WE2E_COMPREHENSIVE_TESTS flag? Thanks!