[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".

Comience con el artefacto driver-bundle y el modelo de dependencias de Maven descritos en el issue; inspeccione cómo se ensamblan y publican actualmente los artefactos de driver y platform. Compare el grafo de dependencias resultante con los artefactos propuestos driver-chromium y específicos de cada plataforma, y considere el trabajo completo cuando los usuarios puedan excluir drivers y plataformas no utilizados sin perder las partes compartidas necesarias.