BFD-4248: Send Release and Deploy BFD Workflow run status updates to Slack

[jonathan-cantu-icf]

JIRA Ticket:
BFD-4248

What Does This PR Do?

Enables and implements Slack Webhooks for BFD GitHub build and deploy workflow.

What Should Reviewers Watch For?

Watch the GitHub Actions for this PR during quality checks.

What Security Implications Does This PR Have?

Please indicate if this PR does any of the following:

• Adds any new software dependencies

• Modifies any security controls

• Adds new transmission or storage of data

• Any other changes that could possibly affect security?

• I have considered the above security implications as it relates to this PR. (If one or more of the above apply, it cannot be merged without the ISSO or team security engineer's (@sb-benohe) approval.)

• I have created tests to sufficiently ensure the reliability of my code, if applicable. If this is a modification to an existing piece of code, I have audited the associated tests to ensure everything works as expected.

Validation

Have you fully verified and tested these changes? Is the acceptance criteria met? Please provide reproducible testing instructions, code snippets, or screenshots as applicable.
The validation will be in seeing what comes out of GitHub quality checks for this PR once the changes are pushed.

[jonathan-cantu-icf]

Performed some rudimentary testing and discovered that there was some deprecated code in the CDAP GitHub Actions function I pulled in to obtain the Slack Webhook:

notify-startNode.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cmsgov/cdap/actions/aws-params-env-action@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

So we may want to address that before fully deploying and implementing this PR.

[mjburling]

[..]
notify-startNode.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cmsgov/cdap/actions/aws-params-env-action@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

So we may want to address that before fully deploying and implementing this PR.

@mianava worked through these details last week: CMSgov/cdap#444

[malessi]

Just a few things!

The issue was addressed.

[sb-benohe]

LGTM: thanks for masking the ARNs + the Pinning of the actions!