Feature #3407 Update METbaseimage version to 13.0

[georgemccabe]

...after the TCDiag seg fault has been resolved

Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  

Ran MET testing workflow with Docker image created from METbaseimage branch and confirmed all tests, including the TCDiag test that was failing), are now passing

https://github.com/dtcenter/MET/actions/runs/33523420631

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

• Ensure all tests pass
• Consider if there is a better way to reference the current base image version number in multiple places to reduce the amount of work needed to update it.
• Consider triggering a METplus testing workflow with the Docker image created from this PR to ensure that all METplus use cases run successfully with these changes

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]

• Do these changes include sufficient testing updates? [Yes]

• Will this PR result in changes to the MET test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Will this PR result in changes to existing METplus Use Cases? [No]
  
  If yes, create a new Update Truth METplus issue to describe them.

• Do these changes introduce new SonarQube findings? [No]
  
  If yes, please describe:

• Please complete this pull request review by 9/4/2026.
  

Pull Request Checklist

See the METplus Workflow for details.

• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Milestone as the version that will include these changes
  Select: METplus-X.Y Support project for bugfix releases or MET-X.Y Development project for the next coordinated release
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[JohnHalleyGotway]

@georgemccabe, as recommended in the PR, I update the logic to define the MET base repo and tag in a single location, a new script named get_met_base_image.sh.

The logic is factored out of the existing set_job_controls.sh script.

Please take a look to see if you're comfortable with this change.

[georgemccabe]

@JohnHalleyGotway, the changes you made to consolidate the base image version is great! Thank you for doing that. There are a few things that I think should be done with these changes.

1. Since the default values for MET_BASE_REPO and MET_BASE_TAG have been removed from the Dockerfiles, we should update the README.md file in internal/scripts/docker to include them as build arguments in the examples since they are now required to be set.

2. It looks like the dtcenter/met DockerHub repository still has build rules set to build tagged releases. This will break because the internal/scripts/docker/hooks/build file does not include the new required build arguments. Automating these builds in DockerHub is redundant since we build the release images via GHA. I suggest that we remove the hooks/build file and disable the automated builds in DockerHub.

[georgemccabe]

@JohnHalleyGotway, a couple other suggestions/thoughts:

3. We may also want to consider setting a default of MET_BASE_REPO=met-base in the Dockerfiles since that is a good default value to use if a user wants to build a Docker image themselves. This gets overridden by our GHA workflows, but it is the logical choice for users running manually and won't change from version to version.

4. Since the version number for the base image is now consistent with the MET version number, we could pull that value from the MET code and utilize the METplus component_versions.py script, if necessary.