feat(drivers): ensure support for `drivername://` URIs

[ianmcook]

What feature or improvement would you like to see?

All the drivers maintained in the adbc-drivers GitHub org now support passing all connection arguments in a URI that starts with drivername://. And most or all of the driver managers now support searching for drivers based on the URI scheme when the driver is not otherwise specified. However, the SQLite driver maintained in this repo does not accept URIs that begin with sqlite://. I believe the Flight SQL driver here also lacks support for URIs that begin with flightsql://. The former should be simple enough to support. The latter might be awkward because the driver already accepts other schemes like grpc+tcp:// and it needs to pass full the URI down to the Flight SQL layer and where the scheme is meaningful.

[lidavidm]

CC @Mandukhai-Alimaa. We might want to file sub-issues for SQLite and Flight SQL separately, and propose what the URI format for Flight SQL would look like.

[amoeba]

I think we should document this too, maybe we need a separate issue. If I'm building a driver, how would I know to handle the uri option and how would I know to how to handle it? I'm not sure this lives in the API standard but maybe a new page?

[ianmcook]

I think we should document this too, maybe we need a separate issue. If I'm building a driver, how would I know to handle the uri option and how would I know to how to handle it? I'm not sure this lives in the API standard but maybe a new page?

Agreed. I'll open a separate issue to document this.

[ianmcook]

#4454

[Mandukhai-Alimaa]

I don't seem to have the permission to create sub-issues. So I created 2 separate issues and assigned them to myself. @lidavidm, I think you can add them as sub-issues here.