fix(ci): Fix Bazel failure Slack message in agw-workflow

[vktng]

Summary

The failure reporting step was not triggered on failure. We have to still include failure() to override the default status check of success() that is automatically applied to if conditions that don't contain a status check function.

Test Plan

CI.
Also tested on fork: https://github.com/vktng/magma/runs/6917739513?check_suite_focus=true

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[nstng]

lgtm, nice to figure out that success() is added implicitly 👍

[github-actions]

dp-workflow

18 tests   18 ✔️  4m 33s ⏱️
  2 suites    0 💤
  2 files      0 ❌

Results for commit fe1214a.

[github-actions]

agw-workflow

     79 files     124 suites   6m 46s ⏱️
1 153 tests 1 149 ✔️ 4 💤 0 ❌
1 155 runs  1 151 ✔️ 4 💤 0 ❌

Results for commit fe1214a.