ArbitraryFileIdManager writes to SQLite database when garbage collected

[davidbrochart]

Description

The ArbitraryFileIdManager does some cleanup in its __del__ method here, which involves writing to a SQLite database.
This creates issues in tests (for example here):

E   pytest.PytestUnraisableExceptionWarning: Exception ignored in: <function ArbitraryFileIdManager.__del__ at 0x7fa08739f920>
E   
E   Traceback (most recent call last):
E     File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/jupyter_server_fileid/manager.py", line 391, in __del__
E       self.con.commit()
E   sqlite3.ProgrammingError: SQLite objects created in a thread can only be used in that same thread. The object was created in thread id 1403275078[56](https://github.com/jupyterlab/jupyter-collaboration/actions/runs/8603265131/job/23574762141?pr=279#step:6:57)256 and this is thread id 140327414023744.

In general, I don't think it is a good practice because the object can be garbage-collected from a different thread that the one in which it was created.
A better solution would be to do this in the teardown of the extension.