Register and enable View-based access control for Quarkus

[mshabarov]

View-based access control Vaadin feature is enabled automatically in Spring-based Vaadin applications if an extension of VaadinWebSecurity class is configured.

Same approach can be done for Quarkus applications, so that developers don't need to instantiate ViewAccessChecker explicitly and create their own VaadinServiceInitListener.

See this comment and this solution for more context.

[mcollovati]

A couple of additional notes:

• ViewAccessChecker is now deprecated, so the focus should be on NavigationAccessControl
• NavigationAccessControl might be enabled by default only if Quarkus security dependency is present (e.g. in a build step)
• We might have to introduce some additional classes to the extension to configure or disable NavigationAccessControl by defining (similar to NavigationAccessControlConfigurer in spring add-on)

Probably not in the scope of this ticket, but additional improvement borrowed from Vaadin and Spring Security integration could be:

• Implement an HttpSecurityPolicy to define basic URL permissions (like we do in VaadinWebSecurity)
• Add AuthenticationContext and pluggable logout handler support.

Here's the link to a repository with an example of integration of Quarkus Security with Vaadin. It is a bit outdated, but may help to give an idea for a potential implementation: https://github.com/mcollovati/flow-quarkus-security-example/tree/main