[pkg/winperfcounters] Improve error when a performance counter fails to scrape

[BinaryFissionGames]

Is your feature request related to a problem? Please describe.

When a performance counter fails to scrape, the IIS receiver logs that an error occurred, along with the error, but not with which counter the error occurred. This information is useful because it helps to understand what metric might be missing.

See:

opentelemetry-collector-contrib/receiver/iisreceiver/scraper.go

Line 91 in b323b9f

rcvr.params.Logger.Warn("some performance counters could not be scraped; ", zap.Error(err))

Describe the solution you'd like

Place the counter path in in the error returned by the PerfCounterWatcher; This will give more context to the error which will aid in debugging issues on live systems.

Describe alternatives you've considered

I considered just logging it in the IIS receiver, but it would be more helpful to have this information in any receiver where this can fail. Adding this information to the error is more useful.

Additional context

No response

[BinaryFissionGames]

I'll be looking into making this change

[github-actions]

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