fix: avoid duckdb locks in testing docs

[euri10]

Description

• some doc tests fails because of a lock in analytics.duckdb, see https://github.com/litestar-org/sqlspec/actions/runs/19490777147/job/55782406206 for instance
• this should fix it

Closes

[euri10]

it still fails randomly between this commit and the last one, there is no reason one works and the other not as he change is just a typo

FAILED docs/examples/usage/usage_drivers_and_querying_10.py::test_example_10_duckdb_config - _duckdb.IOException: IO Error: Could not set lock on file "/home/runner/work/sqlspec/sqlspec/analytics.duckdb": Conflicting lock is held in /home/runner/.local/share/uv/python/cpython-3.10.19-linux-x86_64-gnu/bin/python3.10 (PID 2210). See also https://duckdb.org/docs/stable/connect/concurrency

i guess it is whether or not pytest xdist picks on the same / or not same process, but I thought using at tmp_path would mean different files but i might be incorrect on that ,

any idea @cofin I see marks in tests maybe we can mark duckdb tests to run on the same process ?

[euri10]

ok seems like it is good now