Feature 1833 main v10.0 discussions

[jprestop]

Pull Request Testing

• Describe testing already performed for these changes:
  

Reviewed the changes on the following pages to ensure the references from met_help were changed to Discussions and that the formatting looked correct:
https://met.readthedocs.io/en/feature_1833_main_v10.0_discussions/Users_Guide/index.html
https://met.readthedocs.io/en/feature_1833_main_v10.0_discussions/Users_Guide/tc-pairs.html
https://met.readthedocs.io/en/feature_1833_main_v10.0_discussions/Users_Guide/appendixA.html
https://met.readthedocs.io/en/feature_1833_main_v10.0_discussions/Users_Guide/overview.html

Additionally, I removed references to met_help in the following files:
met/data/wrappers/read_tmp_ascii.py
met/configure.ac

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

Review the changes on the following pages to ensure the references from met_help were changed to Discussions and that the formatting looks correct:
https://met.readthedocs.io/en/feature_1833_main_v10.0_discussions/Users_Guide/index.html
https://met.readthedocs.io/en/feature_1833_main_v10.0_discussions/Users_Guide/tc-pairs.html
https://met.readthedocs.io/en/feature_1833_main_v10.0_discussions/Users_Guide/appendixA.html
https://met.readthedocs.io/en/feature_1833_main_v10.0_discussions/Users_Guide/overview.html

Please review the changes in the following files as well:
met/data/wrappers/read_tmp_ascii.py
met/configure.ac

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

• Please complete this pull request review by [07/13/21].
  

Pull Request Checklist

See the METplus Workflow for details.

• 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 Linked issues with the original issue number.
• 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.

[JohnHalleyGotway]

These changes look fine to me. I approve.