V6 to V7 Upgrade: OIDC (Authentik) User Cannot See Existing Workspaces Due to New UUID Generation

# Problem Description

I deployed Huly via Docker Compose for self-hosting. After upgrading from V6 to V7, I logged in using OIDC (Authentik) authentication, but found that I could no longer see all the Workspaces created before the upgrade.

After investigation, the root cause was identified as:

When logging in via OIDC, the system generated a new user UUID for the same account. The old user UUID still remains in the database, but the new user is not associated with the existing Workspaces.

# Steps to Reproduce

Deploy Huly V6 using Docker Compose.
Enable OIDC authentication (Authentik) and disable local accounts.
Create multiple Workspaces and use the system normally.
Upgrade Huly to V7 following the official guide.
Restore the database data.
Log in using the same OIDC account.
Result: None of the historical Workspaces are visible.

# Current Workaround & Question

Currently, I can only manually add the association between the user and Workspaces via database SQL.

Is there any other configuration method to make the system automatically associate the new user UUID with the old Workspaces upon OIDC login?