[receiver/dockerstats] Add inspect metrics

[carlossscastro]

Description:

Adds 3 new metrics from the docker inspect api

• container.cpu.limit
• container.cpu.shares
• container.restart.count

Since all these metrics are collected from the inspect api, a new method was created (recordInspectMetrics) where only the containerJSON structure is passed as an argument.

Link to tracking Issue: #21087

Testing:

New metrics were added to the receiver test and expected_metrics.yaml files.
The receiver and config tests were also adjusted to reflect the minimum api version of 1.25

❯ go clean -testcache
❯ make test
go test -race -timeout 300s -parallel 4 --tags="" ./...
ok  	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver	0.508s
ok  	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver/internal/metadata	0.381s
❯ go test --tags integration ./...
ok  	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver	14.060s
ok  	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver/internal/metadata	0.241s

Documentation:
New metrics documentation was generated using mdatagen

[andrzej-stencel]

Shouldn't container.restart.count rather be named container.restarts?

According to the spec, count should only be used on namespaces. Is container.restarts a namespace that can include other metrics? If not, we should use container.restarts without the count suffix.

[gbbr]

Thanks for adding this Carlos! Left a small comment, hope it helps :)

[fatsheep9146]

here is a failed check

Error: ../../receiver/dockerstatsreceiver/receiver.go:124:14: r.recordHostConfigMetrics undefined (type *metricsReceiver has no field or method recordHostConfigMetrics)
Error: ../../receiver/dockerstatsreceiver/receiver.go:287:10: use of package receiver not in selector

@sigilioso

[sigilioso]

Thanks for the heads up! It was an issue with one of the latest updates from main. It is fixed now: c374199

[gbbr]

Why is this PR not getting merged? I see that everything is addressed and it has plenty of approvals.