feat(ui): Requests info for Cpu and Mem added to Pod details

[surajyadav1108]

Resolves issue: #19457

1. Added the pod requests info to the Pod tooltip.

• This will only show if the pod currently has some reserved requests (running pods with allocated requests).

• When the pod completes successfully or fails with an error, the requests will be shown as 0 since they are no longer reserved. (also if the resources aren't declared )

2. For the original request of adding the top/parent resource groups,

• there wasn't a good place to add a hover. Instead, I added an info div, similar to the one used for creation and revision, for the group. The tooltip on hover shows the combined requests for the group.

Added tests in info.go f and utils.test for scenerios of completed and failed state with allocated resources.

https://github.com/user-attachments/assets/11d02a4f-e576-4f9a-85e4-dd012715e4be

Checklist:

• [ ] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• [x] The title of the PR states what changed and the related issues number (used for the release note).
• [x] The title of the PR conforms to the Toolchain Guide
• [x] I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• [ ] I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• [ ] Does this PR require documentation updates?
• [ ] I've updated documentation as required by this PR.
• [x] I have signed off all my commits as required by DCO
• [x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• [x] My build is green (troubleshooting builds).
• [ ] My new feature complies with the feature status guidelines.
• [ ] I have added a brief description of why this PR is necessary and/or what this PR solves.
• [ ] Optional. My organization is added to USERS.md.
• [ ] Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[bunnyshell[bot]]

🔴 Preview Environment stopped on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

• 🔵 /bns:start to start the environment
• :rocket: /bns:deploy to redeploy the environment
• :x: /bns:delete to remove the environment

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 55.00%. Comparing base (7f6340f) to head (5cfc8ca). Report is 1 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #20637 +/- ## ========================================== + Coverage 54.99% 55.00% +0.01% ========================================== Files 324 324 Lines 55466 55472 +6 ========================================== + Hits 30505 30515 +10 + Misses 22341 22330 -11 - Partials 2620 2627 +7 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.