feat!(go): split Flight SQL into its own module

[lidavidm]

This way we don't leak CVEs/dependencies from the driver into the core ADBC package.

Breaking changes:

• package go/adbc/driver/flightsql => go/flightsql
• package go/adbc/sqldriver/flightsql => go/flightsql/sqldriver

Also, driverbase is now exposed.

TODOs

• CI, build
• Get OpenTelemetry (or at least the exporters) out of the core, too
• Regenerate licenses

Closes#4623.

[lidavidm]

I wonder if I should just move driverbase to be part of flightsql (since we don't really expect to export it anyways) to get the OpenTelemetry dependency out of core, or even use the thirdparty driverbase fork

[zeroshade]

I wonder if I should just move driverbase to be part of flightsql (since we don't really expect to export it anyways) to get the OpenTelemetry dependency out of core, or even use the thirdparty driverbase fork

I think that's fine since we have we have https://github.com/adbc-drivers/driverbase-go