Delete beans which should not configured in azure-spring-cloud-autoconfigure

[chenrujun]

• AADWebApplicationConfiguration
  • OAuth2UserService: User may be confused when he configured AADOAuth2UserService but he want to map roles into authorities.
  • OAuth2AuthorizedClientManager we should let customer define this. If we did this, customer will be confused if he want to use password login and oboProvider.
• AADResourceServerConfiguration
  • JwtDecoder: If user configured his own JwtDecoder, a lot if features we provided will not work, which will make user confused. Furthermore, seems all resource-server feature can be done by spring-security natively.
  • DefaultAADResourceServerWebSecurityConfigurerAdapter. This should be configured by customer himself. For example, user want to use web-application and resource-server in one application.
• AADOAuth2ClientConfiguration
  • ClientRegistrationRepository configure this will make our starter can not work with other providers, like google. Related issue: [FEATURE REQ] Make azure-spring-boot-starter-active-directory support work together with other oauth2 provider(like google) #23265
  • OAuth2AuthorizedClientRepository: User should configure this by himself. spring-boot-autoconfigure provided the InMemoryOAuth2AuthorizedClientService, the simplest implementation. In distributed system, in-memory way will not work, user should think about this by himself.
  • OAuth2AuthorizedClientManager: Same as before, this should done by user himself.

[chenrujun]

Closing this issue because related PR has been merged.