drop unnecessary 'kn.activator.proxy' metric/span attribute

[dprotaso]

I was trying to be smart when adding this attribute because I thought the 'tag' would appear in child spans and we could see filter traces that went through the activator. OTel doesn't work that way - it's just adding stuff to the current span (which is already associated with the activator service).

Also regarding metrics - you could use this a filter but it's not necessary since you filter the activator using the container/pod name.

/assign @Cali0707
cc @evankanderson

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.30%. Comparing base (bb17bbb) to head (7b6c403).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16045      +/-   ##
==========================================
+ Coverage   80.22%   80.30%   +0.08%     
==========================================
  Files         214      214              
  Lines       16910    16908       -2     
==========================================
+ Hits        13566    13578      +12     
+ Misses       2984     2971      -13     
+ Partials      360      359       -1     

☔ 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

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

[knative-prow-robot]

@dprotaso: new pull request created: #16047

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.