Decoupled monitoring configuration and deployment

[skabashnyuk]

What does this PR do?

Decoupled monitoring configuration and deployment.
Separated.

• Deployment grafana, Prometheus
• Grafana dashboard
• Grafana config
• Prometheus

In this way, the downstream project can reuse some parts of the monitoring configuration.

What issues does this PR fix or reference?

redhat-developer/rh-che#1336

Release Notes

n/a

Docs PR

n/a

[ibuziuk]

@skabashnyuk looks good, but from osio deployment perspective having single template and multiple cms would be problematic to apply via standard CI/CD procedure. Will it be possible to have only che-monitoring.yaml and che-monitoring.config.yaml for the time being?

[ibuziuk]

@skabashnyuk actually, after thinking a little bit - let's not do any refactoring for the time being and use just one single template like it is used in plugin registry https://github.com/eclipse/che-plugin-registry/blob/master/openshift/che-plugin-registry.yml

PR sent - redhat-developer/che-monitoring#1

[skabashnyuk]

ci-test

[che-bot]

Results of automated E2E tests of Eclipse Che Multiuser on OCP:
Build details
Test report
docker image: eclipseche/che-server:13152
https://github.com/orgs/eclipse/teams/eclipse-che-qa please check this report.