Add otelcol.receiver.solace

[wildum]

PR Description

Add the solace receiver from the Otel contrib repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/solacereceiver

Which issue(s) this PR fixes

Fixes #1993

Notes to the Reviewer

A few things to note:

• I tested it manually using the Solace image. This was not super easy to setup, I wrote a guide in the component for it.
• The upstream component uses a list for the broker but only the first element in the list is used. On Alloy side I decided to use a string to avoid confusion
• The upstream component has a retry policy when the next component fails to consume it. I believe that this can be a problem in Alloy when the component has several consumers: if one of the consumer fails, I think that they will all receive the data again, which might lead to data duplication. I added a warning about this in the doc. I don't think that there is a way around it but I also don't think that this is a big problem because it's unlikely to get two traces consumer at this level. If there is a need for branching, an easy workaround would be to just do the branching in the next component.
• I needed to fix a test because of the special case of having empty ptr structs

PR Checklist

• CHANGELOG.md updated
• Documentation added
• Tests updated
• Config converters updated

[thampiotr]

The upstream component has a retry policy when the next component fails to consume it.

That's odd, no? Any idea why did they add this? Shouldn't this be something done on the runtime level?

[wildum]

That's odd, no? Any idea why did they add this? Shouldn't this be something done on the runtime level?

Yet not a fan of this + it makes their implementation much more complex. This was done 2 years ago, maybe they wanted some extra safety because the component might be spamming a lot? They did not add any other flow control strategy since then but there is also no way around it.