Feature #2340 TCDiag one_time_per_file_flag

[georgemccabe]

Added support for setting one_time_per_file_flag. No changes were needed for the change to lead as it was already configurable via METplus config variable LEAD_SEQ.

Pull Request Testing

• [X] Describe testing already performed for these changes:
  

Added unit test for setting new MET config variable

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

Review changes

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

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

• [X] Will this PR result in changes to the test suite? [No]
  

A new unit test was added but it should still pass

• [X] Please complete this pull request review by 10/24/2023.
  

Pull Request Checklist

See the METplus Workflow for details.

• [X] Add any new Python packages to the METplus Components Python Requirements table.
• [X] Review the source issue metadata (required labels, projects, and milestone).
• [X] Complete the PR definition above.
• [X] Ensure the PR title matches the feature or bugfix branch name.
• [X] 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
• [x] After submitting the PR, select the :gear: 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.

[jvigh]

From @georgemccabe: Jonathan, I created a PR with changes to the TCDiag wrapper that match the latest changes to the MET tool. https://github.com/dtcenter/METplus/pull/2374John, this completes the work that was listed in METplus issue #2340. In the issue you say: This issue is enhance that wrapper as needed, and described below. Rather than creating separate issues for each change, I'm bundling them together into this single issue and assigning it to the beta3 development cycle. If it is more convenient to actually make the changes as we go, please feel free to close this issue, and I'll create a new one for additional changes. I reassigned the issue to beta2 (current cycle). I suggest we close this issue after this PR is merged, then you can reopen it and add a comment for new enhancements as needed. What do you think?

The pull requests for each enhancement will still be tied to the appropriate beta, so the timeline of the changes will be preserved even if the issue is moved from cycle to cycle.

[coveralls]

Pull Request Test Coverage Report for Build 6385352205

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.002%) to 84.864%

---

Totals
Change from base Build 6341220440:	0.002%
Covered Lines:	8113
Relevant Lines:	9560

---

💛 - Coveralls

[georgemccabe]

@jvigh, these changes include additions to the Glossary and Python Wrappers chapters of the METplus User's Guide to describe the new variable. The details of this setting belong in the MET User's Guide, where it should already be thoroughly documented.