[kubernetes ] Add missing dimention fields

[tetianakravchenko]

Signed-off-by: Tetiana Kravchenko tetiana.kravchenko@elastic.co

What does this PR do?

When working on another PR - #4095 (comment), I've noticed that some dimension fields are missing - mainly for namespace field - at some point namespace related PR was reverted and all dimension fields were removed - #2209.
Also some fields had typos

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-09-06T14:10:32.105+0000

• Duration: 32 min 29 sec

Test stats 🧪

Test	Results
Failed	0
Passed	90
Skipped	0
Total	90

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (0/0)	💚
Files	100.0% (0/0)	💚 2.89
Classes	100.0% (0/0)	💚 2.89
Methods	94.872% (74/78)	👍 5.261
Lines	100.0% (0/0)	💚 8.249
Conditionals	100.0% (0/0)	💚

[jsoriano]

I think that at some point we thought that the rest of dimensions were enough to identify resources, specially the ones that have uids, as they should be unique, at least per cluster. But I guess it doesn't do any harm to add this one more dimension. It is true that there are cases where we may not have uids.