Add WrapDB Entry for ADBC

### What feature or improvement would you like to see?

Now that https://github.com/apache/arrow-adbc/issues/1941 has been completed, a nice follow up would be to add the ADBC drivers to the Meson WrapDB. This would give end users a very simple way to embed ADBC client sources into their own applications.

The one thing that makes ADBC different from other entries in the WrapDB is the fact that many of the components you'd want to distribute are toggled on via options, i.e. if you wanted sqlite built you have to do `meson configure =Dsqlite=true`

I think this means we would declare dependencies for the adbc_sqlite, adbc_postgresql, etc... and the user may have to specify things like:

```python
adbc_sqlite_dep = dependency('adbc_sqlite', default_options: ['sqlite=true'])
adbc_postgresql_dep = dependency('adbc_postgresql', default_options: ['postgresql=true]')
...
```

The above idea was taken from an IRC conversation with @eli-schwartz though there may be other ways as well

Start by reviewing existing Meson WrapDB entries and the ADBC Meson options for drivers such as SQLite and PostgreSQL. The work is done when ADBC drivers can be consumed through WrapDB dependencies and users can enable the requested components through dependency options.

Written by the indexing model from the issue text.