[develop] Bug fix to support the %H format in METplus via printf. (uf…

…s-community#1102)

This bug was encountered when verifying forecast output that has a 2-digit forecast hour in its name. It turns out specifying the METplus format %H to obtain a 2-digit forecast hour in the workflow/verification configuration variable FCST_FN_TEMPLATE (and others) causes an error in the shell script eval_METplus_timestr_tmpl.sh because bash's printf utility does not support the %H format. This fixes that error using a similar approach to the %HHH format for obtaining 3-digit hours.

ush/bash_utils/eval_METplus_timestr_tmpl.sh

@@ -163,9 +163,23 @@ cannot be empty:
 #-----------------------------------------------------------------------
 #
   case "${METplus_time_fmt}" in
-    "%Y%m%d%H"|"%Y%m%d"|"%H%M%S"|"%H")
+    "%Y%m%d%H"|"%Y%m%d"|"%H%M%S")
       fmt="${METplus_time_fmt}"
       ;;
+    "%H")
+#
+# The "%H" format needs to be treated differently depending on if it's
+# formatting a "lead" time type or another (e.g. "init" or "vald") because
+# for "lead", the printf function is used below (which doesn't understand
+# the "%H" format) whereas for the others, the date utility is used (which
+# does understand "%H").
+#
+      if [ "${METplus_time_type}" = "lead" ]; then
+        fmt="%02.0f"
+      else
+        fmt="${METplus_time_fmt}"
+      fi
+      ;;
     "%HHH")
 #
 # Print format assumes that the argument to printf (i.e. the number to