🚧Set up KD-Admin

[kselena]

Complete The Item Below

• [X] I have updated the title without removing the 🚧 emoji.

Description

Install and set up KDAdmin Use this command to install KDAdmin:

  deno run -Ar https://raw.githubusercontent.com/KinsonDigital/kd-admin/preview/installation/install.ts latest

[!NOTE] If the create-pr.ps1 file already exists, the tool will skip the file. If this happens, set the content of the file to the content below:

& "dev-tools/bin/kd-admin" create-pr;

Acceptance Criteria

### The items to complete to satisfy the Definition of Done.
- [x] All unit tests executed and passed locally after PR work is complete. _(Why? Refer to 'Additional Information' below.)_
- [x] kdadmin installed
- [x] Create PR settings set up
- [x] Prepare release settings set up
- [x] Release note generator settings set up
- [x] json setting files formatted (sft alt f) and add line at the end
- [x] Rename the default gen release settings to `prev-gen-release-note-settings.json`
- [x] Production gen release settings file created
- [x] repo names changed accordingly
- [x] Prepare relase PR template files set up (if needed)
- [x] Update json or csproj path

ToDo Items

### The items to complete to satisfy the Definition of Done.
- [x] Change type labels added to this issue.  Refer to the _**Change Type Labels**_ section below.
- [x] Priority label added to this issue.  Refer to the _**Priority Type Labels**_ section below.
- [x] Issue linked to the correct milestone _(if applicable)_.

Issue Dependencies

No response

Related Work

No response

Additional Information:

Unit Tests

Reasons for local unit test execution:

• 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.
• If you notice that the test status check has passed but the test failed locally, please notify a project maintainer!

💡Warning💡 If the unit tests pass remotely and are not executed locally, this means we could be letting a bug slip into production. Though bugs will always exist in some capacity, we should all do our part to help prevent them from happening.

Change Type Labels

Change Type	Label
Bug Fixes	🐛bug
Breaking Changes	🧨breaking changes
New Feature	✨new feature
CICD Changes	♻️cicd
Config Changes	⚙️config
Performance Improvements	🏎️performance
Code Doc Changes	🗒️documentation/code
Product Doc Changes	📝documentation/product

Priority Type Labels

Priority Type	Label
Low Priority	low priority
Medium Priority	medium priority
High Priority	high priority

Code of Conduct

• [X] I agree to follow this project's Code of Conduct.