Lazily instantiate default components in WebAuthnConfigurer

Avoid unnecessary instantiation of MapPublicKeyCredentialUserEntityRepository and MapUserCredentialRepository in WebAuthnConfigurer

In the configure method of WebAuthnConfigurer, Optional.orElse() is currently
used to provide default implementations when specific Beans are not found
in the ApplicationContext.

public class WebAuthnConfigurer<H extends HttpSecurityBuilder<H>>
		extends AbstractHttpConfigurer<WebAuthnConfigurer<H>, H> {
         // ... 
	@Override
	public void configure(H http) {
                 / ...
                 // Uses orElse(): Always instantiates default repositories
		PublicKeyCredentialUserEntityRepository userEntities = getSharedOrBean(http,
				PublicKeyCredentialUserEntityRepository.class)
			.orElse(userEntityRepository());
		UserCredentialRepository userCredentials = getSharedOrBean(http, UserCredentialRepository.class)
			.orElse(userCredentialRepository());
                 / ... 
    } 
} 

However, orElse() evaluates its argument eagerly. As a result,
userEntityRepository() and userCredentialRepository() are always invoked,
instantiating new repository objects even when a corresponding repository
Bean is already present in the ApplicationContext.

This leads to unnecessary object creation each time the configuration
is initialized.

I propose replacing orElse with orElseGet to ensure that the default
repositories are instantiated only when the Optional is empty.

	public void configure(H http) {

                 // Uses orElseGet(): Instantiates only when necessary
		PublicKeyCredentialUserEntityRepository userEntities = getSharedOrBean(http,
				PublicKeyCredentialUserEntityRepository.class)
			.orElseGet(this::userEntityRepository);
		UserCredentialRepository userCredentials = getSharedOrBean(http, UserCredentialRepository.class)
			.orElseGet(this::userCredentialRepository);
    } 

This change aligns with Java Optional best practices by avoiding unnecessary
object creation and ensuring that default components are initialized only
when they are actually needed.

Start at the configure method of WebAuthnConfigurer and inspect userEntityRepository() and userCredentialRepository(). Replace the eager Optional defaults with lazy defaults, then verify that the default repositories are created only when the corresponding ApplicationContext beans are absent.