Update build/config to use pyproject.toml

[VanL]

This pull request ports the information in setup.py and setup.cfg to pyproject.toml and then deletes the setup.* files. As shown, it installs with uv sync and builds with uv build.

[aosingh]

@VanL

Thanks for raising a PR. Could you please explain the rationale behind multi server ?

[VanL]

Context: I am building an application that will allow clients to log into a main application and "load" or "save" a project. For various reasons, we do not want to have the project save entries in the main database. Our current proposed architecture uses sqlite files as "save files" for clients.

These save files are mostly write-once, read-many, but there may be some updates. We were looking at sqlite_rx as a base because it allows a single process to handle reading/writing of a particular database, resolving concurrency issues (at least as far as sqlite is concerned, we need to handle ordering of operations separately).

However, just like we don't want all the client save files in the main db, we don't want them in the same db. Again, think "save file."

As it is currently, I just extended the existing project to serve multiple databases based on a static map. Instead of the plain REQ/REP socket, the multiserver implements a ROUTER/DEALER that then connects to a SQLiteServer instance based essentially on your existing design.

The going-forward plan is to implement an autocreate/autoconnect feature. Instead of just connecting to the dbs statically defined in the database_map, the server will examine the database name and autocreate/autoconnect to the database to serve the connection.

There is more (managing processes/process lifetimes, eviction, security considerations, configuration), but that's where I am going.

[aosingh]

@VanL I am currently reviewing this. Things are a bit slow on my side because I am on parental leave but I hope to merge this soon by next week.