[receiver/aerospikereceiver] Expand scraped metrics.

[dwelch-spike]

Is your feature request related to a problem? Please describe.
Currently the Aerospike receiver scrapes a subset of the key monitoring metrics. This should be expanded to include a metric set similar to the Aerospike Prometheus exporter.

Describe the solution you'd like
Add new metrics until the scraped set is similar to the Aerospike Prometheus exporter. I'm planning to add these in slices by PR. Something like, query metrics, latency metrics, job metrics, misc metrics, etc.

Describe alternatives you've considered
I don't see any alternative solutions. Just add the new metrics. We could stick to a small subset of metrics but I think matching the Prometheus metrics exporter Aerospike already has makes sense.

[dwelch-spike]

I have started on the query metrics here https://github.com/dwelch-spike/opentelemetry-collector-contrib/tree/aerospikereceiver-metrics

[github-actions]

Pinging code owners: @djaglowski @antonblock. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/aerospike: @djaglowski @antonblock

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.