[Proposal] Add support for multiple exporters (e.g., Jaeger, Zipkin)

[Mr-ylk]

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

Currently, the opentelemetry-go-auto-instrumentation library seems to only support the OTLP exporter for telemetry data export. While OTLP is a standard protocol, many users, especially those using existing telemetry systems like Jaeger and Zipkin, might find it beneficial to have native support for exporting trace data directly to these systems.

Describe the solution you'd like

Add support for mainstream telemetry receivers, such as Jaeger and Zipkin, directly within the opentelemetry-go-auto-instrumentation library. This will allow users to configure their preferred exporter without additional middleware or bridges.

Describe alternatives you've considered

Relying on OTLP and implementing bridges (e.g., OTLP-to-Jaeger or OTLP-to-Zipkin). While this approach works, it introduces additional layers of complexity and operational overhead.

Additional context

No response

[123liuziming]

We will add the Zipkin exporter later. Jaeger supports to receive OpenTelemetry data directly, you can use the agent to report to jaeger directly according to https://github.com/alibaba/opentelemetry-go-auto-instrumentation/tree/main/example/demo. Thanks!