feat: Add feature flag for multi block failure messages. (backport #10061)

[mergify]

This is an automatic backport of pull request #10061 done by Mergify.
Cherry-pick of 374f724 has failed:

On branch mergify/bp/release-1.28.x/pr-10061
Your branch is up to date with 'origin/release-1.28.x'.

You are currently cherry-picking commit 374f724de2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   packages/core/src/config/settings.ts

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   packages/app/src/settings.js
	both modified:   packages/kubernetes/src/pipelines/stages/deployManifest/manifestStatus/DeployStatus.tsx

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[spinnakerbot]

Features cannot be merged into release branches. The following commits are not tagged as one of "fix, chore, docs, perf, test":

• a277bbc: feat: Add feature flag for multi block failure messages. (feat: Add feature flag for multi block failure messages. #10061)

Read more about commit conventions and patch releases here.

[ovidiupopa07]

Should be merged after #10063