Enabling AWS CI/testing

[weihuang-jedi]

The purpose of adding this file is to enable CI testing on AWS.

In the long run, we should only have only one Jenkinsfile, but for the purpose of not disrupt our current GW CI testing on NOAA's on-prem machines, we choose to have a different Jenkinsfile (Jenkinsfile4AWS), to test on AWS, when everything workout correctly, we can merge two files together.

Add a new Jenkinsfile also give us the choice of select different test cases on AWS.

Refs #3341

Type of change

• Bug fix (fixes something broken)
• [x ] New feature (adds functionality)
• Maintenance (code refactor, clean-up, new CI test, etc.)

Change characteristics

• Is this a breaking change (a change in existing functionality)? NO
• Does this change require a documentation update? NO
• Does this change require an update to any of the following submodules? NO (If YES, please add a link to any PRs that are pending.)
  • EMC verif-global
  • GDAS
  • GFS-utils
  • GSI
  • GSI-monitor
  • GSI-utils
  • UFS-utils
  • UFS-weather-model
  • wxflow

How has this been tested?

This is a new feature, which will be tested on AWS.

Checklist

• Any dependent changes have been merged and published
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have documented my code, including function, input, and output descriptions
• My changes generate no new warnings
• New and existing tests pass with my changes
• This change is covered by an existing CI test or a new one has been added
• Any new scripts have been added to the .github/CODEOWNERS file with owners
• I have made corresponding changes to the system documentation if necessary

[weihuang-jedi]

Terry and Walter,

Kris and I have chatted on how to enable CI testing on AWS. We feel that we should:

1. Create a new Jenkinsfile, here Jenkinsfile4AWS as a start point. We choose to start with a different Jenkinsfile, so we won't break any existing on-prem machines CI/testing. When everything workout, we can then have a new PR to merge two files together, if need to.
2. Duplicate Terry's CI workflow, and modify it for AWS.
3. schedule a test and see how it goes.
4. fix any problems along the way.

If possible, could you please give it a quick review and approval?

Thanks,

Wei