opentelemetry: set _other for unknown http methods

[jakebennert]

Commit Message

The OpenTelemetry semantic conventions state, for both client and server spans:

---

HTTP request method value SHOULD be “known” to the instrumentation. By default, this convention defines “known” methods as the ones listed in RFC9110, the PATCH method defined in RFC5789 and the QUERY method defined in httpbis-safe-method-w-body.

If the HTTP request method is not known to instrumentation, it MUST set the http.request.method attribute to _OTHER.

---

This PR updates Envoy's OpenTelemetry tracer to align with this standard.

Additional Description

AI was used to generate the code and tests in this PR. I have reviewed – and fully understand – the code.

It should be noted that Envoy's OTel tracer uses http.method instead of the more up-to-date http.request.method. However, I believe there is ongoing work to update these names happening in #45184.

Risk Level

Low

Testing

I've added unit tests that exercise the new code.

Docs Changes

None required

Release Notes

Added a changelog under minor_behavior_changes (area: opentelemetry).

Platform Specific Features

None

[repokitteh-read-only]

Hi @jakebennert, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #45222 was opened by jakebennert.

see: more, trace.

[repokitteh-read-only]

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #45222 was opened by jakebennert.

see: more, trace.