Bugfix #2449 main_v11.0 pdf

[JohnHalleyGotway]

Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  
  Set up the Sphinx/LaTeX toolchain on my Mac to render the docs as both html and pdf and confirmed that both build well again.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Review the RTD build log. See both the HTML and PDF version of the docs built by RTD for this branch. Confirm that the PDF is downloadable and that the CRPS equations in Appendix C render well.

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

• Do these changes include sufficient testing updates? [Yes]
  I considered how we might enhance the documentation GHA workflow to test for this type of problem in the future. And I recommended to @jprestop that she consider include testing the PDF generation in the next version of that workflow.

• Will this PR result in changes to the test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [Mon 2/27/23].
  

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 Development issue 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.

[jprestop]

I have reviewed the RTD build log. and both the HTML and PDF versions of the docs built by RTD for this branch. I confirm that I was able to download the PDF and that the CRPS equations in Appendix C rendered well. I approve this PR.