Refactor Zipkin Receiver to include Protocols in Config

[EOjeah]

Component(s)

receiver/zipkin

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

Feature Request
Refactor zipkin receiver to include protocols in configuration
Current

zipkin:

After

zipkin:
  protocols:
    http:

Describe the solution you'd like

In order to prepare the zipkin receiver for potentially adding a udp receiver as specified in #35620 and reduce the amount of changes associated with one issue.
This issue is to refactor the code to accept zipkin configuration with potentially different protocols. Initially accepted is the current http protocol with this change.
This will match more closely with the configuration in the otlp receiver that accepts both http and grpc
Before

zipkin:

After

zipkin:
  protocols:
    http:

Follow up changes to include udp protocol in another change.

Describe alternatives you've considered

No response

Additional context

Related to #35620

[github-actions]

Pinging code owners:

• receiver/zipkin: @MovieStoreGuy @andrzej-stencel @crobert-1

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[andrzej-stencel]

Given that the Zipkin receiver is one of the oldest components and has been in Beta stability for a long time, I wonder if we can introduce support for UDP without a breaking change?

One approach could be to leave the existing top-level options like endpoint and other HTTP config options unchanged and still supported (possibly deprecated), and use those unless the user provides the protocols option.

[odubajDT]

I like the idea, if possible I would like to work on this issue, also including the upd support if @EOjeah is not working on it already

[EOjeah]

@odubajDT go ahead! I was planning on working on this when I have time in the next few weeks since it's not urgent for me right now.

[andrzej-stencel]

The issue is yours @odubajDT 🚀

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/zipkin: @MovieStoreGuy @andrzej-stencel @crobert-1

See Adding Labels via Comments if you do not have permissions to add labels yourself.