[fix] Make EnableTracing param work correctly in jaeger-v2 query extension

[Frapschen]

Which problem is this PR solving?

• fix jaeger-v2 query extension EnableTracing param not work

Description of the changes

• new tracerProvider only if EnableTracing is true

How was this change tested?

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[codecov]

Codecov Report

❌ Patch coverage is 77.27273% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 96.61%. Comparing base (34d99f7) to head (95e44a5).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...md/jaeger/internal/extension/jaegerquery/server.go	72.22%	3 Missing and 2 partials ⚠️

❌ Your patch status has failed because the patch coverage (77.27%) is below the target coverage (95.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7226      +/-   ##
==========================================
- Coverage   96.62%   96.61%   -0.01%     
==========================================
  Files         378      378              
  Lines       23146    23154       +8     
==========================================
+ Hits        22364    22371       +7     
  Misses        596      596              
- Partials      186      187       +1     

Flag	Coverage Δ
badger_v1	9.04% <ø> (ø)
badger_v2	1.70% <ø> (ø)
cassandra-4.x-v1-manual	11.70% <ø> (ø)
cassandra-4.x-v2-auto	1.69% <ø> (ø)
cassandra-4.x-v2-manual	1.69% <ø> (ø)
cassandra-5.x-v1-manual	11.70% <ø> (ø)
cassandra-5.x-v2-auto	1.69% <ø> (ø)
cassandra-5.x-v2-manual	1.69% <ø> (ø)
elasticsearch-6.x-v1	16.61% <ø> (ø)
elasticsearch-7.x-v1	16.65% <ø> (ø)
elasticsearch-8.x-v1	16.79% <ø> (ø)
elasticsearch-8.x-v2	1.70% <ø> (ø)
elasticsearch-9.x-v2	1.70% <ø> (ø)
grpc_v1	10.24% <ø> (ø)
grpc_v2	1.70% <ø> (ø)
kafka-3.x-v1	9.68% <ø> (ø)
kafka-3.x-v2	1.70% <ø> (ø)
memory_v2	1.70% <ø> (ø)
opensearch-1.x-v1	16.70% <ø> (ø)
opensearch-2.x-v1	16.70% <ø> (ø)
opensearch-2.x-v2	1.70% <ø> (ø)
opensearch-3.x-v2	1.70% <ø> (ø)
query	1.70% <ø> (ø)
tailsampling-processor	0.47% <ø> (ø)
unittests	95.60% <77.27%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[yurishkuro]

In jaeger v1 we always had self-tracing on by default, so I'm not sure how that property was used. It needs to remain on by default with this change.

[Frapschen]

@yurishkuro This PR will disable self-tracing by default. I've checked the latest Jaeger v1, and it is also disabled by default there.

The screenshot is from 1.70

[yurishkuro]

The v1 all-in-one has query tracing on by default, and so is jaeger-v2.

[Frapschen]

@yurishkuro Please review

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You may re-open it if you need more time.