status: needs work

I think there are related test failures. I will look into them as soon as possible

Let's close as discussed in #61756 (TL;DR, we'd need a realworld use case to support this)

@nicolas-grekas I would still add the interface, so that projects wanting to decorate/replace the main uri signer can implement that interface, instead of having to extend the original UriSigner (because the DI in the listener is not done against an interface right now).

I tend to agree with @stof. Being able to replace the one URI signer that is used across an application is a different (and more common) use case than being able to use different signers per controller.

Nah, same as on the other PR: what's the realworld use case?
The class is not final so we're not blocking anyone.
I'd wait for more feedback before adding more complexity to the codebase.