Updating index pattern to match ccs scenario

[gizas]

• Bug

What does this PR do?

Updates the index pattern as per discussion here: #6603 (comment)

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.

Related issues

• Relates Use *metrics-* as index pattern for adHocDataviews used in Kubernetes Cluster Overview dashboard #6603

[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: 2023-07-12T11:36:32.375+0000

• Duration: 31 min 0 sec

Test stats 🧪

Test	Results
Failed	0
Passed	92
Skipped	0
Total	92

🤖 GitHub comments

Expand to view the 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)	💚
Classes	100.0% (0/0)	💚
Methods	96.154% (75/78)	❕
Lines	100.0% (0/0)	💚
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Package kubernetes - 1.43.1 containing this change is available at https://epr.elastic.co/search?package=kubernetes