adds workspace support as well as support forextends in the config. This now works:

./postgrestools.jsonc

{// ...my linter config}

./project_one/postgrestools.jsonc

{"extends":"../postgrestools.jsonc"// e.g. add specific db config for this project}

Will need to check if client-side changes are required to enable workspace support there.

A few internal changes:

• we now store both the schema cache and the db connection per connection and not globally
• the connections have a idle timeout of a few minutes after which we drop the connection from the cache
• we select the current project when the user opens a file. this is the same pattern biome uses and I think it makes sense.
• EDIT: I want to check if we even need to track the current project since all requests should include the path from which we can find the correct one -> we cannot easily do that. I would go with the current approach for now and maybe do it in a follow up with a better analysis.
• EDIT: Will fix windows path issues for tests 🥲 -> done
• EDIT: Will remove all the windows debug logs 🥲 -> done

ToDo:

• add methods to workspace api
• migrate schema cache manager to store per-connection
• integration ls
• integration cli
• make test green
• implementtry_from_payload with extends
• add test for extends config

closes#334