feature_510_develop_gha_node20

[lisagoodrich]

Pull Request Testing

• Describe testing already performed for these changes:
  
  I ran the commands John HG listed in the issue.
  I ran the manual testing with the workflow dispatch option for this component after submitting the pull request on this branch, feature_510_develop_gha_node20 and it worked.
  Workflow documentation:
  Actions
  Documentation (left hand side of the page.)
  Run workflow
  (Branch: feature_510_develop_gha_node20)
  Run workflow
  Actions

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Please test to make sure this is working as needed.

• 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 test suite? [INo]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [1/31/24].
  >

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)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• 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.

[jprestop]

Thanks for your work on this @lisagoodrich. This looks good to me. I'll approve and squash and merge and ensure that the warning goes away.