chore: add release success and improved fail slack message

[jenniferarnesen]

There are 2 types of commits to the master branch:

1. merge commits that contain the actual code changes
2. the "chore (release)" commit that updates the version in package.json and adds the release notes

These 2 commits to master should have slightly different workflows

1. merge commits (code)

• check code quality using: lint, test, build, e2e
• create the "chore (release)" commit
• report failure if any of the previous checks failed

2. "chore (release)" commit

• build (bc of new package.json version)
• create the new tag
• report failure if any of the previous steps failed
• report success if the tag was created

Another way to describe this:

• PR commit to master
  build, lint, test, e2e, release, release-failure-message

• chore (release) commit to master
  build, tag, release-failure-message or release-success-message

[dhis2-bot]

🚀 Deployed on https://pr-2777--dhis2-data-visualizer.netlify.app

[cypress]

Passing run #2539 ↗︎

0

453

1

0

0

Details:

Merge 6b17077 into ba1fcf5...
Project: Data Visualizer App	Commit: 78695946ad ℹ️
Status: Passed	Duration: 20:15 💡
Started: Nov 9, 2023 11:27 PM	Ended: Nov 9, 2023 11:47 PM

Review all test suite changes for PR #2777 ↗︎

[jenniferarnesen]

Different approach needed