[Azure Monitor] Fix dimensions for CassandraConnectionClosures

[zmoog]

What does this PR do?

Move the CassandraConnectionClosures metric into a dedicated query section using the supported dimension ClosureReason instead of the unsupported DatabaseName.

Why is this important?

We must remediate an error introduced in the previous PR when we put the CassandraConnectionClosures metric name together with other Cassandra-related metrics using the DatabaseName dimension.

This can work under some circumstances — that's why we didn't spot the problem!

Unfortunately, this can cause an error since the CassandraConnectionClosures supports only the ClosureReason and Region dimensions.

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 [Azure Metrics] the integration fails with the "metric names configured CassandraConnectionClosures are not supported for the resource" error #5453

[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-03-08T14:58:04.907+0000

• Duration: 13 min 9 sec

Test stats 🧪

Test	Results
Failed	0
Passed	134
Skipped	0
Total	134

🤖 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% (3/3)	💚
Files	100.0% (3/3)	💚
Classes	100.0% (3/3)	💚
Methods	73.333% (22/30)	👎 -26.667
Lines	100.0% (21/21)	💚 12.621
Conditionals	100.0% (0/0)	💚

[elasticmachine]

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