Content release failure notifications provide detailed information about the source of failure

[jefflbrauer]

Issue Description

As an VFS engineer, I can tell from reading a slack notification, the source of a content release failure, so that I know who is accountable for triage.

---

Tasks

• [ ] Update CI/CD notification process to send detailed content release failure details

Acceptance Criteria

• [ ] Slack notifications from content release failures sent to the #vfs-engineers channel include a description of the source of the release failure (when known) including a distinction for broken links

• ---

  How to configure this issue

• [ ] Attached to a Milestone (when will this be completed?)
• [x] Attached to an Epic (what body of work is this a part of?)
• [x] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
• [x] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
• [x] Labeled with Type (bug, request, discovery, documentation, etc.)

[meganhkelley]

On hold until migration to GHA is complete