Describe the bug
Disconnecting a sqlite connection does not truly close it

To Reproduce
Steps to reproduce the behavior:

1. Create a local sqlite database (tested with sqlite 3.40.1)

   sqlite3 /tmp/foo.db "PRAGMA journal_mode=wal; CREATE TABLE IF NOT EXISTS foo (bar INT);"

2. Create/save a new connection to the sqlite database
3. Connect to it. The small green dot will appear, indicating that it is connected
4. Because of the wal mode, new files will appear, like foo.db-shm and foo.db-wal, which will serve as evidence
5. Right click, disconnect, the green dot disappears. Back to the menu to connect to the database
6. The file foo.db-shm and foo.db-wal are still present, preventing any other app to perform some low level operation
7. Quit the application. The connection will be truly terminated and the extra files will disappear.

Expected behavior
The connection to sqlite database is supposed to be fully closed when disconnecting from the database

Screenshots
If applicable, add screenshots to help explain your problem.

Application (please complete the following information):

• SQLite 3.40.1 (provided by debian packages)
• Antares-SQL, 0.7.16, via deb on Debian 12.1 amd64

Additional context
Untested with any other connection to other database, only sqlite.