fix(otel-collector-config): Jaeger is not a valid exporter for t…

[xuesongbj]

Jaeger is not a valid exporter for the latest Otelm collector. Currently the following exports are allowed:

  - debug
  - logging
  - otlp
  - azuredataexplorer
  - googlecloud
  - influxdb
  - prometheusremotewrite
  - datadog
  - instana
  - mezmo
  - sapm
  - signalfx
  - otlphttp
  - azuremonitor
  - cassandra
  - dataset
  - opencensus
  - awscloudwatchlogs
  - googlemanagedprometheus
  - logicmonitor
  - loki
  - tencentcloud_logservice
  - file
  - alibabacloud_logservice
  - awsemf
  - awskinesis
  - awsxray
  - carbon
  - clickhouse
  - dynatrace
  - loadbalancing
  - sumologic
  - f5cloud
  - kafka
  - prometheus
  - sentry
  - skywalking
  - zipkin
  - awss3
  - elasticsearch
  - logzio
  - pulsar
  - splunk_hec
  - coralogix
  - googlecloudpubsub
  - tan
  - zuobservability

To fix, Change to otlp:

otlp:
    endpoint: jaeger:4317
    tls:
      insecure: true

[helio-frota]

@xuesongbj thanks for your time and contribution.

But please see #84

The repository is part of a blog post https://developers.redhat.com/articles/2023/03/22/how-enable-opentelemetry-traces-react-applications

...and stop updating the code

I have to admit it was my fault for not archiving the repository, but I had to wait a bit in that time.
Either way I'll archive ( since the repository is part of a blog post, if we change the code we will need to update the blog in some form ).

Also, I'm in another team.

Thanks again and sorry for the delay in responding.