E2E fail slack notification + scheduled API tests

[AliaksandrRyzhou]

We want to be informed about how e2e tests are going.

These changes will add the Slack notification when e2e tests fail to tell us that a workflow has been disabled.

Also, as it was discussed here I've added API tests to the schedule

[linear]

INF-388 Slack alert when scheduled e2e fails

[netlify]

✅ Deploy Preview for dev-web-novu ready!

Name	Link
🔨 Latest commit	03f232f
🔍 Latest deploy log	https://app.netlify.com/sites/dev-web-novu/deploys/663a2580fa1c2600081cbb6e
😎 Deploy Preview	https://deploy-preview-5500--dev-web-novu.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for novu-design ready!

Name	Link
🔨 Latest commit	03f232f
🔍 Latest deploy log	https://app.netlify.com/sites/novu-design/deploys/663a2580cd72280007339076
😎 Deploy Preview	https://deploy-preview-5500--novu-design.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rifont]

Awesome work @AliaksandrRyzhou , very clean! Added one question for review, it's non-blocking. ⚡

[rifont]

❓ question: Why is the always() expression (ref to docs) needed here? It seems redundant when the inputs.slack_notification is taking effect already‏

[AliaksandrRyzhou]

@rifont if some step of the merge-reports job fails then a job stops on a failed step and we won't receive a notification. Because the merge-reports job is a part of WEB tests we have to get a notification even when this job fails.