Update the PR template to be consistent with contributing guidelines

PR #650

Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua>

Author: musicinmybrain

.github/PULL_REQUEST_TEMPLATE.md

@@ -21,12 +21,14 @@
   * The format is <Name> <Surname>.
   * Please keep the list in alphabetical order, the file is sorted by name.
 - [ ] Add a new news fragment into the `CHANGES` folder
-  * name it `<issue_id>.<type>` for example (588.bugfix)
+  * name it `<issue_id>.<category>` for example (588.bugfix)
   * if you don't have an `issue_id` change it to the pr id after creating the pr
-  * ensure type is one of the following:
-    * `.feature`: Signifying a new feature.
+  * ensure category is one of the following:
     * `.bugfix`: Signifying a bug fix.
+    * `.feature`: Signifying a new feature.
+    * `.breaking`: Signifying a breaking change or removal of something public.
     * `.doc`: Signifying a documentation improvement.
-    * `.removal`: Signifying a deprecation or removal of public API.
-    * `.misc`: A ticket has been closed, but it is not of interest to users.
+    * `.packaging`: Signifying a packaging or tooling change that may be relevant to downstreams.
+    * `.contrib`: Signifying an improvement to the contributor/development experience.
+    * `.misc`: Anything that does not fit the above; usually, something not of interest to users.
   * Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

CHANGES/650.contrib

@@ -0,0 +1,3 @@
+The pull request template to be consistent with :ref:`the contributing guidelines
+<adding change notes with your prs>`, particularly the list of categories
+-- by :user:`musicinmybrain`.