Bug fixes to "Schedule Monthly" and "WR Schedule Monthly" workflows

[t-will-gillis]

Fixes #8596

What changes did you make?

• trim-inactive-members.md added non-PR contribution label
• trim-inactive-members.js added await closePrework()
• same file changed fs.writeFile() to fs.writeFileSync()
• create-new-issue.js returned the issue.html_url and replaced let with const
• wr-schedule-monthly.yml changes
• Includes default permissions from PR Add default permissions to "Schedule Monthly" and "WR Schedule Monthly" workflows #8611

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

• Label will prevent check-closed-issue-for-linked-pr.yml from reopening issue
• The await is needed because the function has an await; prevents race condition
• Needed for similar reasons to prevent race condition
• Need to use correct variable
• Simplifies YML and cleans up "Close-New-Issue" by removing extraneous code

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
• Test logs- schedule-monthly.yml
• Test logs- wr-schedule-monthly.yml

[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 t-will-gillis-bug-fix-schedule-monthly-8596 gh-pages
git pull https://github.com/t-will-gillis/website.git bug-fix-schedule-monthly-8596