[BUG] Some request too long errors do not produce metrics.

Describe the bug

We have seen the following error in the otel_logs source:

2025-03-10T17:43:22.030 [armeria-common-worker-epoll-3-4] WARN com.linecorp.armeria.server.DefaultUnloggedExceptionsReporter - Observed 1 exception(s) that didn't reach a LoggingService in the last 10000ms(10000000000ns). Please consider adding a LoggingService as the outermost decorator to get detailed error logs. One of the thrown exceptions:
com.linecorp.armeria.common.ContentTooLargeException: maxContentLength: 1048576
...
at java.base/java.lang.Thread.run(Thread.java:833) [?:?]
Caused by: io.netty.handler.codec.compression.DecompressionException: Decompression buffer has reached maximum size: 1048576

This is not resulting in a metric for requestsTooLarge.

To Reproduce

N/A

Expected behavior

1. There should be no stack trace exception. Maybe a single line.
2. The metric should report that there was a request too large.

Screenshots

N/A

Environment (please complete the following information):

N/A

Additional context

N/A

Start by searching the otel_logs source for requestsTooLarge and the handling of ContentTooLargeException or DecompressionException. Trace how oversized requests are reported and check the related tests, if present. Done means these errors produce the expected metric and no unwanted stack trace.