Spring Security SecuredAuthorizationManager should cache annotation's value

SecurityAuthorizationManager currently caches an AuthorizationManager per method/class pair.

The memory footprint this requires can be improved by instead caching the annotation's value and passing that into an instance of the class indicated in #12231.

Comment From: evgeniycheban

@jzheaux I can take this.

Comment From: evgeniycheban

Hi, @jzheaux I created a PR that brings changes for SecuredAuthorizationManager to use the new AuthorizationManager that was added earlier.