🚧Create release workflow

[kselena]

Feature Pull Request

📋Review Checklist📋

• [x] The head(source) branch for this pull request is a 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: feature/- Example: feature/123-my-feature ```

• [x] The head(source) branch for this pull request is created from a development branch with the name develop.

• [x] The base(target) branch for this pull request is a development branch with the name develop.

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

💡For more information on branching, refer to the project's branching documentation.

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

  • One issue per pull request.

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

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

• [x] The assigned project matches the project of the associated issue.

• [x] The assigned milestone matches the milestone of 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] 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.
  • Status checks run for this pull request when merging into the develop 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.

[kselena]

Note PR and issue put on https://github.com/KinsonDigital/BranchValidator/labels/on%20hold Reason: Waiting for the cicd scripts to be added to the org repo and to update the release workflow

[KinsonDigitalAdmin]

Note Taken off of https://github.com/KinsonDigital/BranchValidator/labels/on%20hold status. Concept with org level deno scripts works perfectly.