Spring Add default handling for disconnected client errors to Spring MVC

Spring MVC has default handling for AsyncRequestNotUsableException after #33225 which is raised by our response wrapper when the response fails during an async request. However, the Servlet container may also notify via onError of the IOException, and if that gets through first, it remains unresolved, and that brings unnecessary logging.

WebFlux has default handling for disconnected client errors. We need to add similar in Spring MVC.

Comment From: rstoyanchev

Fixed in 9252e741e17d2a810bf084235016692779518ecc but commit references unrelated issue.