Refactored GHA Code for issue-trigger.yml

[xnealcarson]

Fixes #8151

What changes did you make?

• Refactored the issue-trigger.yml file to replace the external tspascoal/get-user-teams-membership with our existing, internal check-team-membership.js module within the
• Made a copy of the issue-trigger.yml file, issue-trigger2.yml in order to enable the GitHub Action (GHA)
• Test triggered the GHA is by opening a new issue within my own repo. (Test Issue link: Test Issue xnealcarson/website#14)

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

• We already have the check-team-membership.js utility, so we should use it.
• With the external module, we are relying on someone outside of the organization to keep the code current.
• If we use the internal utility function, we are able to eliminate the TEAMS secret & TEAMS token.
• Reorder of the workflow steps so that team membership is checked first since this is the controlling step.

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

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 xnealcarson-replace-external-gha-module-8151 gh-pages
git pull https://github.com/xnealcarson/website.git replace-external-gha-module-8151

[t-will-gillis]

Hey @xnealcarson Looks great!

• Branches are good
• Issue is linked
• There are good descriptions of what is changing and why
• A test run is linked
• No visual changes

Everything looks great- please delete issue-trigger2.yml and this is good to go!

[xnealcarson]

Hey @t-will-gillis . I've gone ahead and deleted issue-trigger2.yml.

[t-will-gillis]

Awesome thanks @xnealcarson !

[santiseccovidal]

Hi @xnealcarson
Everything looks great. Branches and code changes are correct, I also run the changes in my own repo and it works as expected. Check it here

The explanation of the What and Why sections are clear and descriptive.

Thanks for working on this.