de-duplicate targets from portNumber annotation

[j6nca]

We ran into an issue where sidecar containers (i.e vault agent) get registered as targets due to inheriting the pod's annotations for autodiscovery and resulting in alloy scraping the pod multiple times. This fix does a similar check as the portName check above it, and removes these additional targets if the portNumber annotation is specified and the container does not have a corresponding port number exposed.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[petewall]

Please try things again with the latest (2.0.0-rc.13). I fixed an issue with duplicate port scraping.
I actually don't want the portNumber annotation to check for exposed ports, because sometimes, the metrics port is not exposed, but we need to explicitly set it to something. Only checking for exposed ports prevents this option.

[petewall]

I'm going to close this, as we can't take a solution that requires the port number to be exposed.
Try with the latest version and see if that helps!