Modify wrappers that use wrapped MET config files to default to parm/met_config versions if unset

[georgemccabe]

With the recent changes to how MET configs are overridden via METplus, it is rare that a user will want to override the X_CONFIG_FILE variables to another file.

Describe the Enhancement

We should make these variables (i.e. TC_PAIRS_CONFIG_FILE) optional and default to using the wrapped version, i.e. {PARM_BASE}/met_config/TCPairsConfig_wrapped.

Time Estimate

<1 day

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

7740181

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

• Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
• Select milestone to next major version milestone or "Future Versions"

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdatadb, 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.
• 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), Project(s), Milestone, and Linked issues
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[georgemccabe]

ASCII2NC and STATAnalysis config files are optional, so a default value should not be set for those tools.

[georgemccabe]

Code changes were merged via PR #1037 but as @jprestop noted, we should update the documentation to add info to the glossary items for the CONFIG_FILE variables to note the default file that is used if it is unset.

[georgemccabe]

Updates to documentation made in commit 8c9c51c. Closing issue.