Issue with sessions in pgAdmin4

Please note that security bugs or issues should be reported to security@pgadmin.org.

Describe the bug
An issue with pgAdmin4 sessions

To Reproduce

Steps to reproduce the behavior:

1. Install pgAdmin 4 (v6.21) using wheel package (considering all fresh pgAdmin setup)
2. Create a user (test@test.com) and login
3. Add new Servers (using import/export servers) and connect with the server
4. Keep open the browser windows with the test@test.com user logged in
5. Now uninstall pgAdmin and remove the DB file as well
6. Now Install pgAdmin 4 v7.0
7. Create a user (sample@test.com) and log in
8. Add new Servers (using import/export servers)
9. check the server which was connected with V6.21 is showing as connected even though we have not connected it with the latest installation.

Expected behavior

It should not use the older session with the new login
(Note: use fs_uniquifier from the User model to create a new session)

Desktop (please complete the following information):

• OS: OSX Ventura
• Version: Candidate build V7.0
• Mode: Server
• Browser (if running in server mode): chrome
• Package type: Python

Start with the User model and the session handling used by the Python package, using the reported fs_uniquifier note as the entry point. Reproduce the uninstall, database removal, reinstall, and new-login sequence described in the issue. Done means a session from the previous installation is not reused after the new user logs in.