Clica restore breaks API tokens

[LoZio]

Describe the bug
Once a clica restore is done there's no way to generate a valid API token

To Reproduce
Steps to reproduce the behavior:

1. Server A: clica full backup using a token named "Backup"
2. Server B: create a new CA instance, empty, with a brand new token for restore named "Restore"
3. Restore backup from Server A to server B using clica and the "Restore" token
4. Restore completes successfully, data, is present
5. In Server B I can now see the original token "Backup"
6. That token gives 401 access denied using clica.py
7. Delete that token, generate a new one (repeated lots of times). Use the brand new token. Always 401

This is repeatable, did this on a couple of different setups.

Expected behavior
After restore the original token used for the backup should still work.
New token should work too.

Screenshots

Environment (please complete the following information):
Docker instance on Debian 13
Version:
v3.11.1
Build:
67b589f
Infrastructure:
P-FS

[LoZio]

Also newly created users (Global Admin) can only create invalid tokens.