Create epic issue template for GitHub handles 8543

[yielderdev]

Fixes #8543

What changes did you make?

• Created new template file .github/ISSUE_TEMPLATE/issue-making-populate-github-handle-for-project.md in which the markdown from this comment was appended to the issue's indicated YAML front matter to create the GitHub epic issue template.
• While copying the linked issue's YAML front matter into the new template file, I corrected a syntax error present in the source text: an unescaped apostrophe in the about: field.

Why did you make the changes (we will use this info to test)?

• We need to create a template to make an epic issue for each project that has github-handle variables to be populated
• The about: field in the linked issue's YAML front matter contained an unescaped apostrophe, which broke the YAML string syntax and caused parsing to fail. As a result the template was not appearing as a selectable option when creating a new issue.

CodeQL Alerts

After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.

Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown

Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.

• I have checked this PR for CodeQL alerts and none were found.
• I found CodeQL alert(s), and (select one):
  • I have resolved the CodeQL alert(s) as noted
  • I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
  • I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)

Instructions for resolving CodeQL alerts

If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.

In general, CodeQL alerts should be resolved prior to PR reviews and merging

For Reviewers

• Use this URL to check the updated issue template: https://github.com/yielderdev/website/issues/new?template=issue-making-populate-github-handle-for-project.md

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

• No visual changes to the website

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

---

From your project repository, check out a new branch and test the changes.

git checkout -b yielderdev-create-epic-issue-template-for-github-handles-8543 gh-pages
git pull https://github.com/yielderdev/website.git create-epic-issue-template-for-github-handles-8543

[yielderdev]

I noticed #8543 's Overview mentions the template should reference the GitHub-handle spreadsheet and have the person using the epic fill it out, but that step isn't present in the linked comment I copied from. I'm happy to add an action item for it, or perhaps it's handled elsewhere, either way I figured I should flag it.

[jjam02]

Avail: 12pm-4pm PST Everyday
ETA of review 9/8 End of day