CI: Fix GHA failure notification trigger condition

[michaeldiamant]

Amends the trigger condition for Github Action (GHA) failure notification so that it only reaches out when the branch being built matches master or a release branch.

From the docs in https://docs.github.com/en/actions/learn-github-actions/contexts:

Property name	Type	Description
github.base_ref	string	The base_ref or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either pull_request or pull_request_target.
github.ref_name	string	The short ref name of the branch or tag that triggered the workflow run. This value matches the branch or tag name shown on GitHub. For example, feature-branch-1.

Details:

• I'm not sure of the original intent in https://github.com/algorand/go-algorand/pull/4791/files#diff-5c3fa597431eda03ac3339ae6bf7f05e1a50d6fc7333679ec38e21b337cb6721L48, but based on the docs, I think the desired behavior is ref_name.
• a275d96 is tested in Catchpoints: Enrich catchpoint generation and status with KV metadata #4808 (produces no notification) and cherry-picked into this PR.

[codecov]

Codecov Report

Merging #4810 (07f00a6) into master (bffd703) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4810      +/-   ##
==========================================
- Coverage   54.67%   54.66%   -0.01%     
==========================================
  Files         414      414              
  Lines       53550    53550              
==========================================
- Hits        29279    29275       -4     
- Misses      21843    21847       +4     
  Partials     2428     2428              

Impacted Files	Coverage Δ
ledger/roundlru.go	90.56% <0.00%> (-5.67%)	⬇️
network/wsPeer.go	66.50% <0.00%> (-1.95%)	⬇️
ledger/testing/randomAccounts.go	56.61% <0.00%> (+0.61%)	⬆️
ledger/blockqueue.go	88.50% <0.00%> (+2.87%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[algojack]

@michaeldiamant can we clarify here are we trying to have notifications for

1. PRs that target(base) master/rel* branches or
2. the builds that happen after merging

I think with this PR we are switching from 1 to 2. Please correct me if i misunderstand the description.

[michaeldiamant]

I think with this PR we are switching from 1 to 2.

@algojack Correct. That's what I had intended to do in #4791.

[algojack]

Seems like this is intentional. so LGTM.

[algobarb]

I think this change is correct to change from base_ref to ref_name.

It might be a separate discussion on whether we only want to notify on failures for these particular branches.