Strip closing keywords from the body

[rak-phillip]

Summary

This attempts to strip closing keywords from the body of a backport PR.

Occurred changes and/or fixed issues

• Strip closing keywords from the body

Technical notes summary

Previous attempts to prevent altering backport PR milestones haven't worked. I think that a straightforward approach will be to attempt removal of closing keywords from the PR body, this should stop the .github/workflows/scripts/pr-gh-project.js script from altering the milestone based on the linked issues.

Areas or cases that should be tested

Backporting PRs should no longer set the milestone to that of the original issue.

Areas which could experience regressions

This change could inadvertently clobber the body of the backport PR in undefined ways.

Screenshot/Video

NA

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility

[codyrancher]

I'm fine with the change. I did have one thought though. May instead of replacing with white space we do something like "Original text redacted by port-pr.yaml" to avoid confusion and make it easier to track in the future.

[rak-phillip]

I'm fine with the change. I did have one thought though. May instead of replacing with white space we do something like "Original text redacted by port-pr.yaml" to avoid confusion and make it easier to track in the future.

I like this approach. Ready for another review.