Prepping v5.5.2 release

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# These owners will be the default owners for everything in the repo. Unless a later match takes precedence, @bmarshall511, as primary maintainer will be requested for review when someone opens a Pull Request.
+*                   @bmarshall511

.github/ISSUE_TEMPLATE/1-bug-report.yml

@@ -0,0 +1,70 @@
+name: "\U0001F41B Bug report"
+description: "Report a bug with this project."
+labels: "type:bug"
+body:
+    - type: markdown
+      attributes:
+          value: |
+              Thanks for taking the time to fill out this bug report!  Please fill in as much of the template below as you can.
+    - type: textarea
+      attributes:
+          label: Describe the bug
+          description: Please write a clear and concise description of the bug, including what you expect to happen and what is currently happening.
+          placeholder: |
+              Feature '...' is not working properly. I expect '...' to happen, but '...' happens instead
+      validations:
+          required: true
+
+    - type: textarea
+      attributes:
+          label: Steps to Reproduce
+          description: Please write the steps needed to reproduce the bug.
+          placeholder: |
+              1. Go to '...'
+              2. Click on '...'
+              3. Scroll down to '...'
+              4. See error
+      validations:
+          required: true
+
+    - type: textarea
+      attributes:
+          label: Screenshots, screen recording, code snippet
+          description: |
+              If possible, please upload a screenshot or screen recording which demonstrates the bug. You can use LIEcap to create a GIF screen recording: https://www.cockos.com/licecap/
+              Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+              For small snippets paste it directly here, or you can use GitHub Gist to share multiple code files: https://gist.github.com
+              Please ensure the shared code can be used by a developer to reproduce the issue—ideally it can be copied into a local development environment or executed in a browser console to help debug the issue
+      validations:
+          required: false
+
+    - type: textarea
+      attributes:
+          label: Environment information
+          placeholder: |
+             - Device: <!-- [e.g. MacBook] -->
+             - OS: <!-- [e.g. MacOS 10.14.3] -->
+             - Browser and version: <!-- [e.g. Firefox 65.0.1, Chrome 73.0.3683.75, Safari 12.0.3] -->
+      validations:
+          required: false
+
+    - type: textarea
+      attributes:
+          label: WordPress information
+          placeholder: |
+             <!-- If your WordPress version is below 5.2, then please provide your WordPress, Plugins, Themes versions here. -->
+             <!-- If your WordPress version is 5.2 or higher, then please fill out the Site Health Info details below. -->
+             <details><summary>Site Health info:</summary>
+             <!-- Go to Tools > Site Health > Info tab, click "Copy site info to clipboard", and paste those details here. -->
+             </details>
+      validations:
+          required: false
+
+    - type: checkboxes
+      id: terms
+      attributes:
+        label: Code of Conduct
+        description: By submitting this issue, you agree to follow our `Code of Conduct` (see the `CODE_OF_CONDUCT.md` file in the repo).
+        options:
+          - label: I agree to follow this project's Code of Conduct
+            required: true

.github/ISSUE_TEMPLATE/2-enhancement.yml

@@ -0,0 +1,44 @@
+name: "\U0001F680 Enhancement"
+description: "Suggest an idea for this project."
+labels: "type:enhancement"
+body:
+    - type: markdown
+      attributes:
+          value: |
+              Thank you for suggesting an idea to make things better.  Please fill in as much of the template below as you can.
+    - type: textarea
+      attributes:
+          label: Is your enhancement related to a problem? Please describe.
+          description: Please describe the problem you are trying to solve.
+          placeholder: |
+              I use this project as a `...` and I would like `...` so that `...describe benefit...`.
+      validations:
+          required: true
+
+    - type: textarea
+      attributes:
+          label: Designs
+          description: |
+              If applicable, add mockups/screenshots/etc. to help explain your idea.
+              Tip: You can attach images or videos by clicking this area to highlight it and then dragging files in.
+      validations:
+          required: false
+
+    - type: textarea
+      attributes:
+          label: Describe alternatives you've considered
+          description: |
+              Please describe alternative solutions or features you have considered.
+          placeholder: |
+             I have also considered `...describe alternative...`, however I feel that my solution described above is better because of `...reason...`.
+      validations:
+          required: false
+
+    - type: checkboxes
+      id: terms
+      attributes:
+        label: Code of Conduct
+        description: By submitting this issue, you agree to follow our `Code of Conduct` (see the `CODE_OF_CONDUCT.md` file in the repo).
+        options:
+          - label: I agree to follow this project's Code of Conduct
+            required: true

.github/ISSUE_TEMPLATE/3-help.yml

@@ -0,0 +1,23 @@
+name: "❓ Need help?"
+description: "Ask us a question, we are here to help!"
+labels: "type:question"
+body:
+    - type: markdown
+      attributes:
+          value: |
+              If you have a question that is neither a bug report nor an enhancement, then please post it here!  Please fill in as much of the template below as you can.
+    - type: textarea
+      attributes:
+          label: Describe your question
+          description: A clear and concise description of what your question is.
+      validations:
+          required: true
+
+    - type: checkboxes
+      id: terms
+      attributes:
+        label: Code of Conduct
+        description: By submitting this issue, you agree to follow our `Code of Conduct` (see the `CODE_OF_CONDUCT.md` file in the repo).
+        options:
+          - label: I agree to follow this project's Code of Conduct
+            required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,44 @@
+<!--
+Filling out this template is required.  Any PR that does not include enough information to be reviewed may be closed at a maintainers' discretion.  All new code requires documentation and tests to ensure against regressions.
+-->
+
+### Description of the Change
+<!--
+We must be able to understand the design of your change from this description.  The maintainer reviewing this PR may not have worked with this code recently, so please provide as much detail as possible.
+
+Where possible, please also include:
+- verification steps to ensure your change has the desired effects and has not introduced any regressions
+- any benefits that will be realized
+- any alternative implementations or possible drawbacks that you considered
+- screenshots or screencasts
+-->
+
+<!-- Enter any applicable Issue number(s) here that will be closed/resolved by this PR. -->
+Closes #
+
+### How to test the Change
+<!-- Please provide steps on how to test or validate that the change in this PR works as described. -->
+
+### Changelog Entry
+<!--
+Please include a summary for this PR, noting whether this is something being Added / Changed / Deprecated / Removed / Fixed / or Security related.  You can replace the sample entries after this comment block with the single changelog entry line for this PR. -->
+> Added - New feature
+> Changed - Existing functionality
+> Deprecated - Soon-to-be removed feature
+> Removed - Feature
+> Fixed - Bug fix
+> Security - Vulnerability
+
+
+### Credits
+<!-- Please list any and all contributors on this PR so that they can be added to this projects CREDITS.md file. -->
+Props @username, @username2, ...
+
+
+### Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you are unsure about any of these, please ask for clarification.  We are here to help! -->
+- [ ] I agree to follow this project's [**Code of Conduct**](https://github.com/Highfivery/.github/blob/trunk/CODE_OF_CONDUCT.md).
+- [ ] I have updated the documentation accordingly.
+- [ ] I have added tests to cover my change.
+- [ ] All new and existing tests pass.

.github/SAVED_REPLIES.md

@@ -0,0 +1,75 @@
+# Highfivery Saved Replies
+
+In order to help reduce the time it takes to respond to open Issues and Pull Requests, we should leverage [GitHub’s Saved Replies](https://help.github.com/en/articles/about-saved-replies) to help when we are continually responding in the same manner.  The following are various Saved Replies that the Highfivery team should use to respond to Issues and Pull Requests to ensure our community responses are similar and to minimize the amount of time crafting the same response to different requests.
+
+Since GitHub currently does not allow us to have a repository-wide or organization-wide list of [saved replies](https://help.github.com/articles/working-with-saved-replies/), these replies need to be maintained by individual team members.  Since the replies can be modified in the future, all responses are versioned to simplify the process of keeping the replies up to date.
+
+While these Saved Replies attempt to give you the ability to quickly reply to Issues and Pull Requests, they are not meant to be the _exact_ response you should use every time.  Consider customizing them to fit the context of the Issue or Pull Request contribution you are replying to.  You will be best served by welcoming the contributor to the project (if its their first issue/PR), thanking them for their contribution, giving them context to your response (especially if you're closing their issue/PR), and noting next steps (e.g., issue milestoned for a specific release, open to them submitting a PR to resolve an issue, sending a PR to someone else to review).
+
+You can add these saved replies to [your personal GitHub account here](https://github.com/settings/replies).
+
+_Sources: [1](https://github.com/angular/angular/blob/master/docs/SAVED_REPLIES.md), [2](https://github.com/angular/angular-cli/blob/master/.github/SAVED_REPLIES.md), [3](https://github.com/prometheus/docs/blob/master/snippets/saved_replies.md), & [4](https://gist.github.com/jywarren/c9a80e0e53f42208974683aa01c623c8)._
+
+## Issue: already fixed (v1)
+```
+Thanks for filing this Issue!  Fortunately it is now obsolete due to changes in a recent release.  Please update to the most recent version to resolve the problem.
+
+If you are still having problems after updating, then please provide additional details for us to try and replicate your issue.
+```
+
+## Issue: don't understand (v1)
+```
+I'm sorry but I don't understand the problem you are reporting.  Would you please rephrase your issue so I can attempt to better understand it?
+```
+
+## Issue: can't reproduce (v1)
+```
+Thanks for filing this Issue!  Unfortunately I cannot reproduce the problem following the instructions you provided.  We require that reported issues have reproduction steps that highlights the problem.
+
+If the problem still exists for you, then please include any additional information on how to reproduce it.
+```
+
+## Issue: behaving as expected (v1)
+```
+It appears this behaves as expected.  If you still feel there is an issue, please provide further details on your problem.
+```
+
+## Issue: template missing (v1)
+```
+Thanks for filing this Issue!  Please note that we have Issue templates for [bug](https://github.com/Highfivery/REPONAME/blob/develop/.github/ISSUE_TEMPLATE/1-bug-report.md), [enhancement](https://github.com/Highfivery/REPONAME/blob/develop/.github/ISSUE_TEMPLATE/2-enhancement.md), and [question](https://github.com/Highfivery/REPONAME/blob/develop/.github/ISSUE_TEMPLATE/3-help.md) requests.  I would appreciate it if you could edit your Issue and add in the missing details.
+```
+
+## Issue: PR please? (v1)
+```
+I would love your help on this Issue, would be happy to review a PR for it, and will attempt to provide any assistance you might need.
+```
+
+## Issue or PR: duplicate (v1)
+```
+Thanks for filing this (issue, PR).  However this is a duplicate of an existing (issue, PR) #NUMBER, so I'm closing this but if you think this was in error then don't hesitate to comment.  Otherwise please subscribe to #NUMBER for future updates.
+```
+
+## Issue or PR: close as inactive (v1)
+```
+I'm closing this issue due to inactivity, but please let me know if you're still having problems so I can try to help... thanks!
+```
+
+## Issue or PR: send for help! (v1)
+```
+Thanks for filing this!  Unfortunately I’m uncertain on how to proceed here, so I’m pinging (@maintainer) for their input.
+```
+
+## PR: merging and more (v1)
+```
+This looks perfect, so I'll merge it.  If you are looking for another challenge, then please take a look at our `help-wanted` list: https://github.com/Highfivery/REPONAME/labels/help-wanted.  Thanks!
+```
+
+## PR: template missing (v1)
+```
+Thanks for filing this PR!  Please note that we have a [PR template](https://github.com/Highfivery/REPONAME/blob/develop/.github/PULL_REQUEST_TEMPLATE.md) that is required.  I would appreciate it if you could edit your PR and add in the missing details.
+```
+
+## PR: missing related Issue (v1)
+```
+Thanks for filing this PR!  Please note that we require an Issue for each PR so that approach and other details can be discussed in the Issue while code review can happen in the PR.  I would appreciate it if you could [open an Issue](https://github.com/Highfivery/REPONAME/issues/new/choose) and link it to this PR for further discussion.
+```

.github/dependency-review-config.yml

@@ -0,0 +1,55 @@
+name: GPL-Compatible License Policy
+
+# Possible values: "critical", "high", "moderate", "low"
+# fail-on-severity: critical
+
+# You can only include one of these two options: `allow-licenses` and `deny-licences`
+
+# ([String]). Only allow these licenses (optional)
+# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
+# The following list is an attempt to match exactly what's listed on https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses as GPL Compatible (currently ignoring the FSF Free/Libre and OSI Approved column data from the SPDX License List at https://spdx.org/licenses/):
+allow-licenses:
+- 0BSD
+- AGPL-3.0
+- AGPL-3.0-only
+- Apache-2.0
+- Apache-2.0 AND Apache-2.0 WITH LLVM-exception
+- Apache-2.0 WITH LLVM-exception
+- Artistic-2.0
+- BSD-2-Clause
+- BSD-3-Clause
+- BSL-1.0
+- CC-BY-4.0
+- ECL-2.0
+- EFL-2.0
+- EUDatagrid
+- GPL-2.0
+- GPL-2.0-only
+- GPL-2.0-or-later
+- GPL-3.0
+- GPL-3.0-only
+- GPL-3.0-or-later
+- HPND
+- Intel
+- ISC
+- LGPL-3.0
+- LGPL-3.0-only
+- LGPL-2.1
+- LGPL-2.1-only
+- MIT
+- MPL-2.0
+- NCSA
+- Sleepycat
+- Unlicense
+- UPL-1.0
+- W3C
+- Zlib
+- ZPL-2.0
+# The following licenses fit the above criteria except they are not marked as FSF Free/Libre on the SPDX License List (https://spdx.org/licenses/):  Unicode-DFS-2016
+# The following licenses fit the above criteria except they are not marked as OSI Approved on the SPDX License List (https://spdx.org/licenses/): ClArtistic, CECILL-2.0, BSD-3-Clause-Clear, FTL, iMatix, Imlib2, IJG, OLDAP-2.7, Ruby, SGI-B-2.0, SMLNJ, Vim, WTFPL, X11, XFree86-1.1
+
+# ([String]). Block the pull request on these licenses (optional)
+# Possible values: Any  `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
+# The following list is an attempt to match exactly what's listed on https://www.gnu.org/licenses/license-list.html#GPLIncompatibleLicenses as GPL Incompatible:
+# deny-licenses: AGPL-1.0, AGPL-1.0-only, AFL-1.1, AFL-1.2, AFL-2.0, AFL-2.1, AFL-3.0, Apache-1.1, Apache-1.0, APSL-2.0, BitTorrent-1.0, BSD-4-Clause, CECILL-B, CECILL-C, CDDL-1.0, CPAL-1.0, CPL-1.0, Condor-1.1, EPL-1.0, EPL-2.0, EUPL-1.1, EUPL-1.2, FDK-AAC, gnuplot, IPL-1.0, LPPL-1.3a, LPPL-1.2, LPL-1.02, MS-PL, MS-RL, MPL-1.1, NOSL, NPL-1.0, NPL-1.1, Nokia, OLDAP-2.3, OSL-1.0, OSL-1.1, OSL-2.0, OSL-2.1, OSL-3.0, OpenSSL, PHP-3.01, Python-2.0, QPL-1.0, RPSL-1.0, SISSL, SPL-1.0, xinetd, YPL-1.1, Zend-2.0, Zimbra-1.3, ZPL-1.1
+# The following list is an attempt, additionally, to match exactly what's listedn on https://www.gnu.org/licenses/license-list.html#NonFreeSoftwareLicenses as Nonfree: Aladdin, APSL-1.0, APSL-1.1, APSL-1.2, Artistic-1.0, CPOL-1.02, RHeCos-1.1, JSON, NASA-1.3, OPL-1.0, RPL-1.1, Watcom-1.0