Backport of Fix Backport Assistant PR commenting into release/1.15.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #18200 to be assessed for backporting due to the inclusion of the label backport/1.15.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@zalimeni
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

For general comments on a PR, it looks like you have to use the /issue endpoint rather than /pulls, which requires commit/other review-specific target details.

This matches the endpoint used in backport-reminder.yml.

Also remove the noisier Backport Reminder workflow in favor of recent automation to assign backport PRs to authors.

Description

Follow-up to #17197, plus a noise-reduction fix.

Testing & Reproduction steps

Ran:

github_message="Backport failed @zalimeni. Run: [this is a test to fix broken commenting, no link included]"
          curl -s -H "Authorization: token ${PR_COMMENT_TOKEN}" \
            -X POST \
            -d "{ \"body\": \"${github_message}\"}" \
            "https://api.github.com/repos/hashicorp/consul/issues//comments"

and it worked. (I also fat-fingered the PR I meant to target the first time 😛)

PR Checklist

• updated test coverage
• external facing docs updated
• appropriate backport labels added
• not a security concern

---

Overview of commits

• de63f65 - f6c0fff

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR