[release/public-v2.2.0] Fix crontab bug for Cheyenne and Derecho, upd…

…ate PR template for new platforms (#939)

The option to create an experiment with the option USE_CRON_TO_RELAUNCH=True is currently broken on Cheyenne and Derecho due to some bad python logic. This fixes that issue.

Also took the opportunity to update the PR template to include the new supported platforms (Derecho, Hercules, and Gaea C5)

Contains an additional fix for removing old crontab entries on Cheyenne and Derecho

.github/PULL_REQUEST_TEMPLATE

@@ -32,9 +32,12 @@
 
 - [ ] hera.intel
 - [ ] orion.intel
+- [ ] hercules.intel
 - [ ] cheyenne.intel
 - [ ] cheyenne.gnu
+- [ ] derecho.intel
 - [ ] gaea.intel
+- [ ] gaeac5.intel
 - [ ] jet.intel
 - [ ] wcoss2.intel
 - [ ] NOAA Cloud (indicate which platform)

ush/get_crontab_contents.py

@@ -35,11 +35,10 @@ def get_crontab_contents(called_from_cron, machine, debug):
     # themselves being called as cron jobs.  In that case, we must instead
     # call the system version of crontab at /usr/bin/crontab.
     #
-    if machine == "CHEYENNE" or machine == "DERECHO":
+    crontab_cmd = "crontab"
+    if machine.upper() == "CHEYENNE" or machine.upper() == "DERECHO":
         if called_from_cron:
             crontab_cmd = "/usr/bin/crontab"
-    else:
-        crontab_cmd = "crontab"
 
     print_info_msg(
         f"""