fix: visualize CPU and Memory usage with LineProgress in pod list

[HanCheo]

close: #851

1. Fixed an issue where the line progress for CPU and memory was not visible in PodDetailsList.
2. When operating with virtualList, the issue where node names were visible because the hideNode and LinkedPod arguments were not passed to getTableRow has been fixed.

[omarluq]

LGTM thank you for fixing this ❤️ the comment is to address an edge case that your fix exposes but doesn't block your pr

[omarluq]

When testing I found an edge case unrelated to this fix stemming from getPodKubeMetrics:
pods in terminal states (Succeeded or Failed), which never have metrics reported, as well as
pods for which metrics have not yet been collected, result in { cpu: NaN, memory: NaN }.
These NaN values then propagate into the UI.

We have a few options to fix this:

1. UI-level guard (in getTableRow), i.e.

const { cpu, memory } = podStore.getPodKubeMetrics(pod) ?? {};

const safeCpu = Number.isFinite(cpu) ? cpu : 0;
const safeMemory = Number.isFinite(memory) ? memory : 0;    

2. Store-level fix: never return NaN from getPodKubeMetrics. Treat “no metrics available” as 0 usage.

3. Store-level fix: return null to represent “unknown”. This is more semantically correct, but requires UI changes to display and handle sorting

[robertobandini]

Thanks @HanCheo and @omarluq!