Drop probe tracing in queue-proxy

[dprotaso]

I'm noticing when looking at the jaeger traces the queue probes (kubelet/activator) are pretty meaningless since they're not being parented to anything.

Also otelhttp is not filtering them out since we're 'starting' the trace within the queue-proxy. This makes it internal.

/assign @Cali0707
/assign @evankanderson

[dprotaso]

/cherry-pick release-1.19

[knative-prow-robot]

@dprotaso: once the present PR merges, I will cherry-pick it on top of release-1.19 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-1.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.16%. Comparing base (5832a44) to head (58430ed).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/queue/sharedmain/main.go	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16048      +/-   ##
==========================================
- Coverage   80.28%   80.16%   -0.13%     
==========================================
  Files         214      214              
  Lines       16905    16888      -17     
==========================================
- Hits        13572    13538      -34     
- Misses       2972     2989      +17     
  Partials      361      361              

☔ 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.

[Cali0707]

/lgtm

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Cali0707, dprotaso

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dprotaso]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[knative-prow-robot]

@dprotaso: new pull request created: #16050

Details

In response to this:

/cherry-pick release-1.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.