Allow fine tuning of class scanning in FrontendDependencies

[mcollovati]

Describe your motivation

To optimize the production build, the FrontendDependencies class performs a byte-code scan to find all potential frontend dependencies that are referenced by the application.
Currently, to speed up the scan, a list of ignored packages and class name patterns are hard-coded into the class.

While it works well for most of the projects, Flow cannot know all dependencies in advance that a project might use and that do not contain references to frontend packages.
On the other hand, community add-ons may be ignored mistakenly because they are using a package name that Vaadin filters out.

Describe the solution you'd like

In addition to the hard-coded list, allow the developers to configure Maven and Gradle plugins to specify their custom inclusion/exclusion sets.
Inclusion and exclusions can be defined as regular expressions, and if present they override the hard-coded rules (or there can still be a minimal hard-coded exclusion set).

<configuration>
   <frontendScan>
       <excludes>
          <exclude>java|sun|oracle|elemental|javax|javafx|jakarta|oshi|cglib</exclude>
          <exclude>org\.(apache|antlr|atmosphere|aspectj|jsoup|jboss|w3c|spring|joda|hibernate|glassfish|hsqldb|osgi|jooq|springframework|bouncycastle|snakeyaml|keycloak|flywaydb)\b</exclude>
      </excludes>
     <includes>
         <include>com\.application</include>
     <includes>
   </frontendScan>
</configuration>

Describe alternatives you've considered

Vaadin Spring integration already has a concept of filtering that can be adjusted with vaadin.allowed-packages and vaadin.blocked-packages properties.
However, they are used only in development mode for Spring projects and are supposed to be stored in the application.properties files; the build tool plugins currently do not read that file (because it may not be present at all).