✨(ZENKO-5262) Define new alerts and enable monitor for Zenko Operator

[DarkIsDude]

Issue: ZENKO-5262

What does this PR do, and why do we need it?

Define new alerts and enable monitoring of the operator.

https://github.com/scality/zenko-operator/pull/608/changes

Which issue does this PR fix?

Fixes ZENKO-5262.

[bert-e]

Hello darkisdude,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Branches have diverged

This pull request's source branch feature/ZENKO-5262/monitor-operator has diverged from
development/2.14 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the
following solutions:

• Merge origin/development/2.14 into feature/ZENKO-5262/monitor-operator
• Rebase feature/ZENKO-5262/monitor-operator onto origin/development/2.14

Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset command.

[francoisferrand]

usually we keep the alerts along with the components which "owns" these metrics, to reduce coupling and ensure we rename the metrics and alerts/dashboards at the same time.

That would mean both alerts.yaml and building the Oras image would be in Zenko-operator; and in Zenko we would simply need to change the content of zenkoversion to reference zkop's dashboard image (along with the manifest change to enable scraping)

any reason not to do this for these?