Improve response filter documentation

[geoand]

Close: #36955

[famod]

Ah, interesting - confirmed with small reproducer; I only need a matching @ServerExceptionMapper which doesn't need to set the header though!
The irony is that for some reason I tried it via the quickstart right away instead of in my app - and there I already have matching exception handlers. 🤦‍♂️

WDYT about making it more explicit by adding:

Such a reponse filter will also be called for <<exception-mapping, handled>> exceptions.

just above

Your filters may declare any of the following parameter types:

My reasoning here is that you don't need to add the Throwable parameter and your filter will still be called.

[geoand]

I all for making it more clear for readers, but I am not sure I understand how you would like it to look.
If you want to push a change into my branch, that's fine with me :)

[github-actions]

🙈 The PR is closed and the preview is expired.

[famod]

I've pushed what I had in mind.

[geoand]

🙏🏼

[famod]

I've just realized that even a Jakarta-way ContainerResponseFilter is called for mapped exceptions. I'll add a note there too.