SEC-2975: Provide exception handler for TypeMismatchException

Ted Bergeron (Migrated from SEC-2975) said:

See DATACMNS-576: Write an exception handler for TypeMismatchException in an @ControllerAdvice annotated type, inspect the cause and return 403 Forbidden if you find an AccessDeniedException.

Discussed with Oliver issues when trying to apply security to Spring Data repositories. There is a detailed flow described in the linked issue that shows a security exception being swallowed / chained by the spring core framework.

The actual stack trace is a chain of 3 exceptions:

org.springframework.beans.TypeMismatchException: Failed to convert value of type 'java.lang.String' to required type 'com.xyz.Person'; 
nested exception is org.springframework.core.convert.ConversionFailedException: Failed to convert from type java.lang.String to type @org.springframework.web.bind.annotation.PathVariable com.xyz.Person for value '28107749'; 
nested exception is org.springframework.security.access.AccessDeniedException: Access is denied

I have an extension of org.springframework.web.servlet.mvc.method.annotation.ResponseEntityExceptionHandler which is already handling TypeMismatchException. Thus, I overrode the handleTypeMismatch method and added the logic to inspect the rootCause there.

Start with Spring MVC's TypeMismatchException handling and the ResponseEntityExceptionHandler.handleTypeMismatch entry point mentioned in the issue. Trace the nested ConversionFailedException cause chain and verify that a contained AccessDeniedException produces a 403 Forbidden response; otherwise preserve the existing handling behavior.