chore: Remove workflow: add-reviewer-monitoring.yaml

[akrejcir]

What this PR does / why we need it:
Currently the workflow adds comments to PRs too often.

We will make a better solution in a future PR.

Special notes for your reviewer:
This is a partial PR from: #669

Release note:

None

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[akrejcir]

/cc @0xFelix @jcanocan

[0xFelix]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0xFelix

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [0xFelix]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jcanocan]

/lgtm

[kubevirt-bot]

@akrejcir: #874 failed to apply on top of branch "release-v0.19":

Applying: chore: Remove workflow: add-reviewer-monitoring.yaml
Using index info to reconstruct a base tree...
M	.github/workflows/add-reviewer-monitoring.yaml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): .github/workflows/add-reviewer-monitoring.yaml deleted in chore: Remove workflow: add-reviewer-monitoring.yaml and modified in HEAD. Version HEAD of .github/workflows/add-reviewer-monitoring.yaml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 chore: Remove workflow: add-reviewer-monitoring.yaml
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-v0.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.