Move release notes into its own chapter in the User's Guide

[jprestop]

Describe the Task

Move the MET Release Notes section out of the Overview chapter and into it's own chapter (under Overview - the Release Notes will become chapter 2). Rename in the following way:

• 1.5 MET Release Notes -> 2 MET Release Information
• Modify the index.rst file to add the new chapter "release-notes" after "overview"
• Create a new 2.1 section called MET Release Notes
• The existing information in current sections in 1.5.1 - 1.5.3 should be moved to 2.1.1 - 2.1.3.
• Create a new 2.2 section called MET Upgrade Instructions (with paragraph text "Upgrade instructions will be listed here if they are applicable for this release.")

This work will require changing the types of headers to follow the standard guidelines:
https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html

# with overline, for parts
* with overline, for chapters
=, for sections
-, for subsections
^, for subsubsections
“, for paragraphs

Time Estimate

<1 day

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

MET-11.0.0-beta4 release

Funding Source

2792541

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

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

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

Task 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) and Linked issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[lisagoodrich]

My feature branch is : feature_2296_release_notes_move

On the pull request I linked to Move release notes into its own chapter #2298. Please note the numbers are different. I didn't know how to handle this.

[lisagoodrich]

Work is completed.