NEWS: move to docs

Since the release notes are in Markdown now, let's add them to the docs
site.  Add a symlink from the root to make them easier to find in a
tarball or checkout.

Author: bgilbert

.github/ISSUE_TEMPLATE/release-checklist.md

@@ -1,8 +1,8 @@
 Release checklist:
 
 Tagging:
- - [ ] Write release notes in `NEWS.md`. Get them reviewed and merged
-     - [ ] If doing a branched release, also include a PR to merge the `NEWS.md` changes into main
+ - [ ] Write release notes in `docs/release-notes.md`. Get them reviewed and merged
+     - [ ] If doing a branched release, also include a PR to merge the `docs/release-notes.md` changes into main
  - [ ] Ensure your local copy is up to date with the upstream main branch (`[email protected]:coreos/butane.git`)
  - [ ] Ensure your working directory is clean (`git clean -fdx`)
  - [ ] Ensure you can sign commits and any yubikeys/smartcards are plugged in
@@ -49,7 +49,7 @@ GitHub release:
  - [ ] Download the artifacts and signatures
  - [ ] Verify the signatures
  - [ ] Find the new tag in the [GitHub tag list](https://github.com/coreos/butane/tags) and click the triple dots menu, and create a draft release for it.
- - [ ] Upload all the release artifacts and their signatures. Copy and paste the release notes from `NEWS.md` here as well.
+ - [ ] Upload all the release artifacts and their signatures. Copy and paste the release notes from `docs/release-notes.md` here as well.
    - [ ] If the signing key has changed, note the change in the GitHub release notes as done [here](https://github.com/coreos/butane/releases/tag/v0.12.0).
  - [ ] Publish the release
 

NEWS.md

@@ -0,0 +1 @@
+docs/release-notes.md

NEWS.md

@@ -1,5 +1,5 @@
 ---
-nav_order: 9
+nav_order: 10
 ---
 
 # Developing Butane