Internal: Enhance automated testing to properly test main branches

[georgemccabe]

Currently testing is robust for the develop branches. Changes to the develop branch of METplus components such as MET, METdataio, METplotpy, and METcalcpy trigger a METplus use case test run for its develop branch.

Describe the Enhancement

Enhance the testing logic to trigger the default main_vX.Y METplus branch when changes to the components' corresponding main branches occur. It would also be nice to improve the Docker build logic to automatically update the METplus image with any bugfixes applied to the components (or at least MET).

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

• 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

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.
• 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.

[georgemccabe]

This was completed by creating a custom GitHub Action called metplus-action-trigger-use-cases that properly handles triggering of METplus use case tests for both main_vX.Y and develop branches. The above commits show where this was added for the main_vX.Y and develop branches for METdataio, METcalcpy, and METplotpy.

This was added for MET in commits 4e6a889 (develop) and 30bf4fb (main_v12.0).