[Feature] Consider splitting driver dependencies

The driver bundle is one big jar containing all the drivers for every supported platform. This makes it quite large, roughly 117 MB for v1.29.0.

The "driver-bundle" artifact could be changed to be only a very small artifact with runtime dependencies for each driver and platform. This would allow users to exclude drivers and platforms they don't need. For example, if someone only needs Chromium on Windows x86-64, Maven's method of excluding dependencies could be used to reduce the download size.

So, in the future, one could have a variant of "driver-bundle" that includes only the shared parts for all drivers and depends on "driver-chromium" (with shared parts for each platform), "driver-chromium-linux" (Linux parts only), and "driver-chromium-windows" (Windows parts only). "driver-chromium-linux" may also depend on "chromium-linux-x86-64" and "chromium-linux-arm64".

Commencez par l’artefact driver-bundle et le modèle de dépendances Maven décrits dans l’issue ; examinez comment les artefacts actuels de driver et de platform sont assemblés et publiés. Comparez le graphe de dépendances obtenu avec les artefacts proposés driver-chromium et spécifiques à la plateforme, et considérez le travail comme terminé lorsque les utilisateurs peuvent exclure les drivers et les plateformes inutilisés sans perdre les parties partagées requises.