ci: Invoke webhook on PR merge

- This gives us flexibility to create a docs issue from Jira or react differently depending on the PR merge data
- Creating issues in the docs repo is deprecated
- Tested webhook with data in a test repo to ensure PR data could be used correctly

.github/workflows/create-docs-issues.yml → .github/workflows/pr-merge-webhook.yml

@@ -1,4 +1,4 @@
-name: Create documentation ticket
+name: PR Merge Webhook
 
 on:
   pull_request_target:
@@ -10,20 +10,19 @@ on:
 
 jobs:
   create-docs-ticket:
-    # Only on merged PRs that contain the DocumentationNeeded flag
-    if: github.event.pull_request.merged && contains(github.event.pull_request.labels.*.name, 'DocumentationNeeded')
+    # Only on merged PRs
+    if: github.event.pull_request.merged
     runs-on: ubuntu-24.04
     steps:
       - uses: actions/checkout@v4
 
-      - name: Create Issues
-        id: create-issues
-        uses: actions/github-script@v7
-        with:
-          github-token: ${{ secrets.DOCS_ISSUES_PAT }}
-          script: |
-            const script = require('.github/workflows/create-docs-issues.js');
-            await script({github, context});
+      - name: Trigger PR Merge Webhook
+        id: trigger-pr-merge-webhook
+        env:
+          # Push the PR details in the webhook data.
+          WEBHOOK_DATA: ${{ toJSON(github.event.pull_request) }}
+        run: |
+          curl -X POST -H 'X-Automation-Webhook-Token: ${{ secrets.JIRA_WEBHOOK_SECRET_PR_MERGE }}' -H "Content-Type: application/json" --data "$WEBHOOK_DATA" ${{ secrets.JIRA_WEBHOOK_URL_PR_MERGE }}
 
       - name: Slack Failure Message
         uses: slackapi/[email protected]