Infra prometheus collector

[ledbruno]

Proposed changes

In a environment with a single chaos control plane and "many" infrastructure deployments, it's necessary to properly monitor if infrastructure are active or not (Since inactive infras are unable to execute chaos experiments).

Our proposal is to enable a prometheus collector that queries chaoscenter database and exposes all "non-deleted" cluster as gauge metrics (1 active, 0 inactive).

That metric is exposed on litmus-portal/metrics path. (it also exposes golang default metrics)

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Dependency

• Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer: