Wire up awsxrayproxy extension

[anuraaga]

Description:

Adds awsxrayproxy to the contrib components

Link to tracking Issue:

Testing:

Documentation:

[jpkrohling]

Looks like this isn't the only component that isn't wired yet:

$ ls -1 exporter/ > /tmp/exporters-available.txt
$ grep "github.com/open-telemetry/opentelemetry-collector-contrib" internal/components/components.go | sed 's/"//g' | grep exporter | awk -F/ '{print $5}' > /tmp/exporters-wired.txt
$ diff /tmp/exporters-*
2d1
< awscloudwatchlogsexporter
12d10
< elasticsearchexporter
16d13
< googlecloudpubsubexporter
26d22
< observiqexporter
33d28
< skywalkingexporter

Would it make sense to wire them all in a single PR?

[jpkrohling]

Extensions and processors seem to be in sync, but receivers aren't:

$ diff /tmp/receivers-*
1d0
< awscontainerinsightreceiver
5d3
< cloudfoundryreceiver
11,12d8
< googlecloudpubsubreceiver
< googlecloudspannerreceiver
14d9
< httpdreceiver
23,26d17
< memcachedreceiver
< mongodbatlasreceiver
< mysqlreceiver
< nginxreceiver
34d24
< scraperhelper

[anuraaga]

I would need to dig through whether any of those are in-progress (as my awsxrayproxy was until this PR :) ). The guidelines recommend only wiring in when ready

https://github.com/open-telemetry/opentelemetry-collector/blob/main/CONTRIBUTING.md#when-adding-a-new-component

[jpkrohling]

Sounds good, I'll open a separate issue to track that. I thought this was in connection to #5725 :-)

[jcchavezs]

Looks good @anuraaga

[willarmiros]

Do we want to rename to awsproxy in case we want any future service requests proxied through here? Won't block on it since i can't think of any use cases right now, but just a thought for extensibility.

[bogdandrutu]

Please rebase.

[anuraaga]

Thanks went ahead and renamed to awsproxy as suggested

[bogdandrutu]

Please rebase

[bogdandrutu]

@anuraaga not sure if it was a race, but another merge is required :(