feat: Prometheus Metrics Provider Should Evaluate Prometheus Query Before Sending to Prometheus

[liesenfeldn]

This relates to this issue.

I also set up a local kind cluster and tested this. I checked that this works with the templates we are attempting to create, but also i tested some of our old templates to make sure it is backwards compatible.

I mentioned some alternative implementations of this feature in my issue. Specifically i wanted to call out that we could also add a new field called QueryExpression or something similar, that way the Query behavior stays exactly as is, and this features get added in a new field in the struct.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed my commits with DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

[github-actions]

Published E2E Test Results

  4 files    4 suites   3h 9m 9s ⏱️
113 tests 101 ✅  7 💤 5 ❌
458 runs  424 ✅ 28 💤 6 ❌

For more details on these failures, see this check.

Results for commit fd3e231.

♻️ This comment has been updated with latest results.

[github-actions]

Published Unit Test Results

2 298 tests   2 298 ✅  2m 59s ⏱️
  128 suites      0 💤
    1 files        0 ❌

Results for commit fd3e231.

♻️ This comment has been updated with latest results.

[liesenfeldn]

I've checked off the My builds are green. Try syncing with master if they are not. part, because it says all checks have passed, but i'm not sure that was correct, since above it does link to this which indicated e2e test failures. Can someone help me understand this? Thanks!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud