Create and publish a PDF of the MET User's Guide via Read-The-Docs

[JohnHalleyGotway]

Describe the Task

As of met-9.1, the User's Guide is created via Sphinx and the resulting html output is published to:
https://ncar.github.io/MET/index.html

This task is to render the User's and Contributor's Guides as 2 separate PDF files which would useful for offline viewing. Some users, particularly in secure areas, do not have ready access to the internet for viewing docs on github.io.

George McCabe did some initial investigation but ran into issues rendering equations.

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

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
• Select milestone

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdb, METviewer, METexpress, METcalcpy, METplotpy

Task Checklist

See the METplus Workflow for details.

• Complete the issue definition above.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the task and verify your changes.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop and link the pull request to this issue.
  Pull request: feature <Issue Number> <Description>
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[JohnHalleyGotway]

Coordinated with @ksearight and merged the latest from develop into this feature branch:

Auto-merging met/docs/Users_Guide/wavelet-stat.rst
Auto-merging met/docs/Users_Guide/tc-pairs.rst
Auto-merging met/docs/Users_Guide/index.rst
Auto-merging met/docs/Users_Guide/appendixA.rst

Confirmed that the build succeeded on RTD with no warnings generated.
https://readthedocs.org/projects/met/builds/14295247/

[ksearight]

John HG reported the following on July 22 in Slack:
There's a ROC image that's the last item of section 31.4.13. However in the PDF, it gets served up on page 426, inside of section 31.5.1.I only noticed this when adding new documentation from Eric. Any idea how to FORCE the ROC image to stay where we want it? Maybe a manual page break or something?

[ksearight]

merged into develop