bkpaas_auth DjangoAuthUserCompatibleBackend 丢失了用户的time_zone

https://github.com/TencentBlueKing/bkpaas-python-sdk/blob/61976219d7ea78df38de30025e54ffeb7b47e8dd/sdks/bkpaas-auth/bkpaas_auth/backends.py#L180

Reason: bkpaas_auth already declares time_zone as a supported user-info field and already stores it in LoginToken.user_info, but DjangoAuthUserCompatibleBackend.connect_to_django_user() drops it when converting the bkpaas_auth.models.User into the project’s Django AuthUser. That makes any downstream app using the compatible backend unable to read request.user.time_zone.

I’d keep our local subclass as a production hotfix, but file an upstream issue/PR so we can remove the shim after upgrading. The upstream fix should probably copy all relevant transient user-info fields, at minimum:

db_user.display_name = getattr(user, "display_name", user.username)
db_user.tenant_id = getattr(user, "tenant_id", None)
db_user.time_zone = getattr(user, "time_zone", None)

Maybe also review chinese_name, avatar_url, email, etc., because bkpaas_auth.models.AbstractUserWithProvider.USERINFO_FIELDS includes more fields than the compatible backend currently propagates. For our immediate bug, time_zone is the concrete missing field.

Start with sdks/bkpaas-auth/bkpaas_auth/backends.py at DjangoAuthUserCompatibleBackend.connect_to_django_user(), then compare it with bkpaas_auth.models.AbstractUserWithProvider.USERINFO_FIELDS and LoginToken.user_info. Done means the compatible Django AuthUser preserves the concrete time_zone value, with the other supported transient fields reviewed for consistency.