[tooling] Upgrade all dependencies to the latest version

[the-glu]

• Remove constrains about dependencies (UV take care of that for us)
• Upgrade to latests versions

[mickmis]

Reviewed 4086fbe.
I do have some apprehension that such a mass upgrade could silently break some tooling/code paths not covered by the CI (e.g. test scenarios testing encryption of DB communications which directly use psycopg but is not ran in the CI). But the risk is probably acceptable so I'd tend to go ahead with the PR anyway.
@BenjaminPelletier any opinion?

[mickmis]

Discussed during InterUSS weekly: should be OK to go ahead and merge unless specific concern. If something breaks, it should be added in the CI.

I do have concerns about psycopg, notably checking out its release notes. Just 3.1.19 has changes in errors returned (https://www.psycopg.org/psycopg3/docs/news.html#psycopg-3-1-19). As we discussed, adding some unit tests testing the behavior of that scenario using psycopg should address those concerns.
What about:

• not upgrading in this PR psycopg so that we can proceed with merging it
• add unit test in follow-up for psycopg behavior we rely on
• upgrade psycopg
  ?

[the-glu]

* not upgrading in this PR psycopg so that we can proceed with merging it
* add unit test in follow-up for psycopg behavior we rely on
* upgrade psycopg

Yes fine for me, I updated the lock file with psycopg not updated :)