add confmap provider to registry.json

[jackgopack4]

As mentioned in #5387, there are more components that are compatible with the OpenTelemetry Collector.
These include confmap.Converter and confmap.Provider types.

confmap.Converter: open-telemetry/opentelemetry-collector#11582

confmap.Provider: open-telemetry/opentelemetry-collector#4567

There are currently five confmap.Providers that are maintained in the OpenTelemetry Collector core repository and while there is only one Converter there and it is deprecated, there are vendors that make use of converters and it is possible they would choose to publish them in the registry once this is available.

As I am not super familiar with the registry and changes necessary to update the same, I may have missed file(s) that need to be changed and will happily make these changes if suggested.

Additionally, I don't feel strongly about calling them "confmap converter" vs. "converter" or provider, but it seemed slightly more descriptive. Open to feedback there as well.

[jackgopack4]

I will also plan to submit a separate PR to add the existing five confmap.providers to the registry once this change is approved.

[svrnm]

I will also plan to submit a separate PR to add the existing five confmap.providers to the registry once this change is approved.

Can you put all of them in one PR? Makes it easier to validate things and how we are going to name those values.

[jackgopack4]

Can you put all of them in one PR? Makes it easier to validate things and how we are going to name those values.

Yes, done.

[songy23]

LGTM

[svrnm]

Thanks, see some questions and suggestions inlined

[svrnm]

thanks @jackgopack4

[jackgopack4]

ah shoot, this shows "confmap providers" as the yaml tag; is there any way to have the type listed as "Confmap provider" in the dropdown but show "providers" in the sample manifest?

Alternatively I can just change the name to "provider" instead of "confmap provider"