[receiver/jaegerreceiver] Add logs when the respective server starts in jaegerreceiver

[Saumya40-codes]

Description

• This PR adds the logging related to the server starting under the jaegerreceiver
• Added logs when: AgentHTTP, GRPC, Thrift Http, Thrift Binary and Thrift compact server starts

Link to tracking issue

Fixes jaegertracing/jaeger#6412

How was change tested?

Running collector with jaegerreceiver enabled with its all transports

Output

@Saumya40-codes ➜ /workspaces/opentelemetry-collector-contrib (log-endpoints) $ ./bin/otelcontribcol_linux_amd64 --config config.yaml
2024-12-27T15:37:23.428Z        info    service@v0.116.1-0.20241220212031-7c2639723f67/service.go:164   Setting up own telemetry...
2024-12-27T15:37:23.428Z        info    telemetry/metrics.go:70 Serving metrics {"address": "localhost:8888", "metrics level": "Normal"}
2024-12-27T15:37:23.428Z        info    builders/builders.go:26 Development component. May change in the future.        {"kind": "exporter", "data_type": "traces", "name": "debug"}
2024-12-27T15:37:23.436Z        info    service@v0.116.1-0.20241220212031-7c2639723f67/service.go:230   Starting otelcontribcol...      {"Version": "0.116.0-dev", "NumCPU": 2}
2024-12-27T15:37:23.436Z        info    extensions/extensions.go:39     Starting extensions...
2024-12-27T15:37:23.436Z        info    jaegerreceiver@v0.116.0/trace_receiver.go:252   Starting UDP server for Binary Thrift   {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:6831"}
2024-12-27T15:37:23.436Z        info    jaegerreceiver@v0.116.0/trace_receiver.go:274   Starting UDP server for Compact Thrift  {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:6832"}
2024-12-27T15:37:23.436Z        info    jaegerreceiver@v0.116.0/trace_receiver.go:398   Starting HTTP server for Jaeger Collector       {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:14268"}
2024-12-27T15:37:23.436Z        info    jaegerreceiver@v0.116.0/trace_receiver.go:423   Starting gRPC server for Jaeger Collector       {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:14250"}
2024-12-27T15:37:23.436Z        info    service@v0.116.1-0.20241220212031-7c2639723f67/service.go:253   Everything is ready. Begin running and processing data.

config file used

receivers:
  jaeger:
    protocols:
      grpc:
        endpoint: "0.0.0.0:14250"
      thrift_http:
        endpoint: "0.0.0.0:14268"
      thrift_binary:
        endpoint: "0.0.0.0:6831"
      thrift_compact:
        endpoint: "0.0.0.0:6832"
        
exporters:
  debug: {}

service:
  pipelines:
    traces:
      receivers: [jaeger]
      exporters: [debug]

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: yurishkuro / name: Yuri Shkuro (364d4be)
• ✅ login: Saumya40-codes / name: Saumya Shah (19cff4a, 0090b57, adafb33, f3c94d2, 4db9280, 9b8e2ae, c5cd657, 5482948)

[yurishkuro]

please include a sample output of running a collector with jaeger receiver enabled (with all its transports) to show logs in action

[Saumya40-codes]

please include a sample output of running a collector with jaeger receiver enabled (with all its transports) to show logs in action

I've added the same in the PR description. Should anything be changed?

[yurishkuro]

nothing looks odd to you in the output? Why do you need to repeat "kind": "receiver", "name": "jaeger"?

[Saumya40-codes]

nothing looks odd to you in the output? Why do you need to repeat "kind": "receiver", "name": "jaeger"?

Apologies, I overlooked there and didnt identify that it's been updated/added by default.

[yurishkuro]

please add a ./.chloggen/ entry

[yurishkuro]

need to run make gotidy