[TASK] Add namespaceMetrics attribute to GET /workspacekinds API response

[andyatmiami]

Certification

• I certify I am an Epic Owner for Kubeflow Notebooks 2.0 and expected to create planning-related issues.

Description

🛑 This issue is dependent upon completion of #677

Work was originally performed to include a clusterMetrics object on the API response for GET /workspacekinds

• feat(ws): add ws counts to backend wsk model #368

That commit had a few // TODO comments that we want to address as part of this work:

• https://github.com/kubeflow/notebooks/pull/368/files#diff-5a4650065c6e40d76e86fc1df9189efbbdc0d93250c74928b71601e13eac2890R65
• https://github.com/kubeflow/notebooks/pull/368/files#diff-5a4650065c6e40d76e86fc1df9189efbbdc0d93250c74928b71601e13eac2890R110
• https://github.com/kubeflow/notebooks/pull/368/files#diff-5a4650065c6e40d76e86fc1df9189efbbdc0d93250c74928b71601e13eac2890R130

When the namespaceFilter query parameter is provided to the GET /workspacekinds endpoint - the following behavior should occur:

• clusterMetrics attribute is omitted from API response
• namespaceMetrics attribute is included in API response
• "counts" for the namespaceMetrics should be scoped to only the specified namespace as provided in ?namespaceFilter

namespaceMetrics should be typed and handled similarly as clusterMetrics

Acceptance Criteria

• when ?namespaceFilter query parameter IS NOT provided:
  • clusterMetrics attribute included in GET /workspacekinds API response
    • counts included reflect data across all namespaces
  • namespaceMetrics attribute omitted in GET /workspacekinds API response
• when ?namespaceFilter query parameter IS provided:
  • namespaceMetrics attribute included in GET /workspacekinds API response
    • counts included reflect data specific to namespace provided in ?namespaceFilter
  • clusterMetrics attribute omitted in GET /workspacekinds API response