Permanently enable 'telemetry.newPipelineTelemetry' feature gate

[djaglowski]

Discussed offline in relation to #12812

Introduction of this gate had some unintended side effects, such as removing attributes from loggers.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.52%. Comparing base (78663f9) to head (208b49b).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #12856      +/-   ##
==========================================
+ Coverage   91.47%   91.52%   +0.04%     
==========================================
  Files         494      494              
  Lines       26993    26982      -11     
==========================================
+ Hits        24691    24694       +3     
+ Misses       1818     1809       -9     
+ Partials      484      479       -5     

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

[jade-guiton-dd]

LGTM, just two suggestions

[djaglowski]

It's been pointed out elsewhere that since the feature gate being enabled is a workaround for the problems it introduced, it's likely that users will already be using the gate. Therefore, removing it outright would break users.

Our featuregate docs explicitly call out that alpha gates may be immediately deprecated, but also that this is equivalent to permanently disabling the gate. Therefore, from a functionality perspective, stable is the most direct way to lock the gate into a permanently enabled state.

We can also just move the gate along our normal path to beta, but it's unclear that anyone would benefit from disabling the gate, and also IMO sends the wrong message that the gate is progressing as normal.

[djaglowski]

The spell check failure appears to be bogus and unrelated to this PR.