Add prometheus rules

[DebakelOrakel]

Move prometheus rules from openshift4-monitoring component to logging component.

Checklist

• Keep pull requests small so they can be easily reviewed.
• Update the documentation.
• Categorize the PR by setting a good title and adding one of the labels:
  bug, enhancement, documentation, change, breaking, dependency
  as they show up in the changelog
• Link this PR to related issues.

[simu]

LGTM overall, with one big caveat: we lose the functionality of adding custom annotations to openshift-logging alerts and removing individual openshift-logging alerts via parameters.openshift4_monitoring.alerts with this change.

See https://github.com/projectsyn/component-rook-ceph/blob/master/component/alertrules.libsonnet for an example which implements custom annotations and removal of rules. The idea there was that we'd move the core logic for adding custom annotations and removing rules based on the contents of parameters.openshift4_monitoring.alerts to a component library in component openshift4-monitoring, once more components start having a need to make their alert rules ready for OCP4.

[simu]

LGTM, see inline comments for some cleanup and a note regarding recording rules.

[simu]

Comment is just copy-pasted. We should check if the recording rules (if there are any) are actually deployed by the cluster-logging operator, and adjust the filter function if we need to deploy the recording rules ourselves.