[NATS] Add connection data stream dimensions

[gpop63]

What does this PR do?

Adds dimensions for connection data stream.

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

• Relates NATS TSDB Enablement #7745

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: 2023-10-10T21:35:46.703+0000

• Duration: 31 min 7 sec

Test stats 🧪

Test	Results
Failed	0
Passed	31
Skipped	2
Total	33

🤖 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% (1/1)	💚
Files	100.0% (1/1)	💚
Classes	100.0% (1/1)	💚
Methods	100.0% (29/29)	💚
Lines	95.522% (192/201)	❕
Conditionals	100.0% (0/0)	💚

[agithomas]

NATS can be deployed nearly anywhere; on bare metal, in a VM, as a container, inside K8S, on a device, or whichever environment you choose.

Due to this, i would recommend having all common dimension fields included in the list. Please have a look at the TSDB migration guidelines document.

Please have it changed on all PRs, if missing.

[agithomas]

Please have it corrected as - Added dimensions mapping to connection data stream.

[agithomas]

LGTM!

[elasticmachine]

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