Add logic to regenerate previously tagged versions based on a schedule

[JohnHalleyGotway]

Describe the Enhancement

The v3.0 release and tag was created on Sept 6, 2023. However, while working toward the v3.1 release 2 months later, we discovered that the v3.0 tag no longer builds. The issue was that the most recent Python package versions changed and then failed to compile. For v3.1, we added specific Python package version numbers to prevent this in the future.

Recommend defining a schedule for GHA to automatically rebuild existing tags based on a schedule. Or if more convenient, we could use DockerHub to do so. This would ensure that the METbaseimage does not grow stagnant through time and would allow us to easily pull OS patches as they become available.

Note, also recommend updating the Dockerfiles for MET to run apt update to pull also pull any critical OS patches as they become available.

Time Estimate

1 day?

Sub-Issues

Consider breaking the enhancement down into sub-issues.
None.

Relevant Deadlines

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

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy
  No impacts.

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.
• 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 issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.