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 36.36364% with 7 lines in your changes missing coverage. Please review.

Project coverage is 69.78%. Comparing base (208527d) to head (6aa7ba6).
Report is 2 commits behind head on main.

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

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2332      +/-   ##
==========================================
- Coverage   69.85%   69.78%   -0.07%     
==========================================
  Files         361      361              
  Lines       50040    50049       +9     
==========================================
- Hits        34953    34925      -28     
- Misses      14013    14041      +28     
- Partials     1074     1083       +9     

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

[whynowy]

Make sure to handle the configuration change together with the release internally.

[whynowy]

Why is there some logic like this?

[adarsh0728]

I introduced Objects field which can be a list now instead of Object, because there was too much duplicity of patterns in config(handling pipeline and monoVertex separately).

Now, when, frontend wants to know the metrics for monoVertex, we don't want to send the ones with dimension vertex(pipeline). Hence the check

[whynowy]

Discussed offline, need to rethink and refactor the approach of doing configuration as well as the frontend implementation. Approving this PR for now to unblock.