Enhance the Stat Analysis Additional Filename Template Tags

[CPKalb]

Describe the Enhancement

The lead time templates in Stat Analysis do not allow formatting. So, {lead?fmt=%3H} in Stat-Analysis always produces the lead time in HHMMSS (like 030000); the time templates have no effect. The specific tags this applies to are listed below. We should allow formatting for lead time in the Stat-Analysis special templates. Allowing formatting will also mean that we have some redundant tags. I don't know if these are used for another purpose in the wrapper or in use cases, or if they could be removed.

Tags that should allow formatting and currently don't support it:
lead
fcst_lead
obs_lead

Tags that don't allow formatting but will become redundant once formatting is supported in the above tags:
lead_hour
lead_min
lead_sec
lead_totalsec
fcst_lead_hour
fcst_lead_min
fcst_lead_sec
fcst_lead_totalsec
obs_lead_hour
obs_lead_min
obs_lead_sec
obs_lead_totalsec

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as a METplus-Wrappers-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a METplus-Wrappers-X.Y.Z version, select the METplus-Wrappers-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Enhancement Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Add any new Python packages to the METplus Components Python Requirements table.
• For any new datasets, an entry to the METplus Verification Datasets Guide.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the next official version
  Select: METplus-Wrappers-X.Y.Z Development project for development toward the next official release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.