Local driver installs where archive has `.` in path before extension are hard to load with a driver manager

[amoeba]

When I install a driver from a local archive with a . in the path before the extension, the driver essentially gets installed in a way that makes it unloadable with its short name:

$ go run ./cmd/dbc install --no-verify some_driver_unsigned_v1.0.0.tar.gz
Installing from local package: some_driver_unsigned_v1.0.0.tar.gz

[✓] installing
[✓] verifying signature

Installed some_driver_unsigned_v1.0.0 1.10.0 to /Users/bryce/Library/Application Support/ADBC/Drivers


~/src/columnar-tech/dbc docs/local-install*
$ uv run --with "adbc-driver-manager,pyarrow,pandas" python
Python 3.14.0 (main, Oct 14 2025, 21:10:22) [Clang 20.1.4 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> dbapi.connect(driver="sqlite_windows_amd64_v1.10.0")
KeyboardInterrupt
>>> from adbc_driver_manager import dbapi
>>> dbapi.connect(driver="some_driver_unsigned_v1.0.0")
Traceback (most recent call last):
  File "<python-input-1>", line 1, in <module>
    dbapi.connect(driver="some_driver_unsigned_v1.0.0")
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/bryce/.cache/uv/archive-v0/EStS9NB8jX-_IylBAEqtw/lib/python3.14/site-packages/adbc_driver_manager/dbapi.py", line 252, in connect
    db = _lib.AdbcDatabase(**db_kwargs)
  File "adbc_driver_manager/_lib.pyx", line 605, in adbc_driver_manager._lib.AdbcDatabase.__init__
  File "adbc_driver_manager/_lib.pyx", line 262, in adbc_driver_manager._lib.check_error
adbc_driver_manager.ProgrammingError: NOT_FOUND: [Driver Manager] Could not load `some_driver_unsigned_v1.0.0`: dlopen() failed: dlopen(some_driver_unsigned_v1.0.0, 0x0006): tried: 'some_driver_unsigned_v1.0.0' (no such file), '/System/Volumes/Preboot/Cryptexes/OSsome_driver_unsigned_v1.0.0' (no such file), '/usr/lib/some_driver_unsigned_v1.0.0' (no such file, not in dyld cache), 'some_driver_unsigned_v1.0.0' (no such file)                                   dlopen() failed: dlopen(libsome_driver_unsigned_v1.0.0.dylib, 0x0006): tried: 'libsome_driver_unsigned_v1.0.0.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OSlibsome_driver_unsigned_v1.0.0.dylib' (no such file), '/usr/lib/libsome_driver_unsigned_v1.0.0.dylib' (no such file, not in dyld cache), 'libsome_driver_unsigned_v1.0.0.dylib' (no such file)

I think the . causes the driver manager to take a different branch when we would otherwise discover the manifest.

Should dbc's local install mechanism warn or prevent the user from doing this?

[lidavidm]

I ran into this too: #265 (review)

Maybe we should just ask for an explicit name when doing this?