Update/add issue and PR templates

[kselena]

Preview Feature Pull Request

✅Code Review Checklist✅

• [x] The head(source) branch for this pull request is a preview feature branch, with the correct naming syntax, in the following example:

  • A head(source) branch is the branch being merged into a target branch.

    Example

    ``` xml Syntax: preview/feature/- Example: preview/feature/123-my-preview-feature ```

• [x] The head(source) branch for this pull request is created from a preview release branch, with the correct naming syntax, in the following example:

  • A head(source) branch is the branch that is being merged into the base(target) branch.
  Example

  ``` xml Syntax: preview/v..-preview. Example: preview/v1.2.3-preview.4 ```

• [x] The base(target) branch for this pull request is a preview release branch, with the correct naming syntax, in the following example:

  • A base(target) branch is the branch that the head(source) branch is merging into.
  Example

  ``` xml Syntax: preview/v..-preview. Example: preview/v1.2.3-preview.4 ```

• [x] Pull request title matches the title of the associated issue.

• [x] Associated issue exists and is linked to this pull request.

  • One issue per pull request.

• [x] The labels attached to this PR match the labels attached to the associated issue.

• [x] My code follows the coding style of this project.

  • The style is enforced by the .editorconfig files in the project and displayed as warnings. If there is an edge case, reach out and let's discuss it.

• [x] A https://github.com/KinsonDigital/BranchValidator/labels/preview label has been added to the pull request.

• [x] I have manually tested my code changes to the best of my ability.

• [x] All tests passed locally.

  • This is required because unit tests might pass locally but not in the CI environment during the status check process or vice-versa.
  • Tests might pass on the developer's machine but not necessarily on the code reviewer's machine.
  • This does not mean that the tests pass in both the local and CI environment.
  • Status checks run for this pull request when merging into the preview/v*.*.*-preview.* branch. These status checks run every time a change is pushed to the pull request. These checks validate version syntax, tagging, builds, unit tests, and more.

[CalvinWilkinson]

Reverted PR due to developer forgetting to push up the latest changes.