feat: cpu memory metrics

[adarsh0728]

• Adds Memory and CPU pattern in metrics config at pod level
• Adds Memory and CPU pattern in metrics config at container level [filter values added for container dropdown for a particular pod]

[codecov]

Codecov Report

Attention: Patch coverage is 62.50000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 67.47%. Comparing base (05cd792) to head (fa8243e).

Files with missing lines	Patch %	Lines
server/apis/v1/promql_service.go	40.00%	1 Missing and 2 partials ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2332   +/-   ##
=======================================
  Coverage   67.47%   67.47%           
=======================================
  Files         351      351           
  Lines       45822    45827    +5     
=======================================
+ Hits        30918    30922    +4     
  Misses      13828    13828           
- Partials     1076     1077    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[veds-g]

since we are using pod name out of podDetails, can we just pass it instead?

[veds-g]

can we merge monovertex and pipeline patterns for pod and containers, since it is repetitive?

[adarsh0728]

I can think of two ways:

1. Introducing new field (Objects) which is a list. Ensures backward compatibility (no change in existing config), only discovery API needs to check two fields now instead of one.
2. Making Object field as a list. It has an advantage of having single field but have to change Object field for existing patterns and make sure it doesn't break anything.

@veds-g WDYT?

[veds-g]

lets make it Objects which acts as a llist.