Convert issue templates in markdown to GitHub's issue forms

[mitchelbaker-cisa]

🗣 Description

Shout out to Lauren for starting these changes.

Converts markdown versions of "new idea" and "bug report" templates to Github's issue forms.

GitHub documentation if interested.

💭 Motivation and context

This issue would be useful because issue forms encourage specific, structured information we want included in issues, as well as required fields/input validation.

Closes #359

🧪 Testing

Check out 1-newidea.yml and 2-bugreport.yml files for formatting/consistency against the markdown templates: 💡-idea.md and 🐛-bug-report.md

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• If applicable, All future TODOs are captured in issues, which are referenced in the PR description.
• The relevant issues PR resolves are linked preferably via closing keywords.
• All relevant type-of-change labels have been added.
• I have read and agree to the CONTRIBUTING.md document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
  - [ ] Tests have been added and/or modified to cover the changes in this PR.
  - [ ] All new and existing tests pass.

✅ Pre-merge Checklist

• This PR has been smoke tested to ensure main is in a functional state when this PR is merged.
• Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge Checklist

• Delete the branch to clean up.
• Close issues resolved by this PR if the closing keywords did not activate.

[buidav]

@mitchelbaker-cisa will hold off on my approval in case you want to backport any suggestions Ted or Addam have on the M365 equivalent PR that can also apply here cisagov/ScubaGear#1562