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

Issue に記載されている driver-bundle artifact と Maven dependency model から始め、現在の driver artifact と platform artifact がどのように組み立てられ、公開されているかを調査します。得られた dependency graph を、提案されている driver-chromium artifact および platform-specific artifact と比較し、ユーザーが必要な共有部分を失うことなく、使用しない driver と platform を除外できるようになった時点で作業完了とみなします。