chore: update @better-auth/sso and better-auth to version 1.5.0-beta.…

[Siumauricio]

…16; rename session_temp table to session and adjust related constraints; add new SQL migration for session table; implement getTrustedProviders function for dynamic provider retrieval

What is this PR about?

Please describe in a short paragraph what this PR is about.

Checklist

Before submitting this PR, please make sure that:

• You created a dedicated branch based on the canary branch.
• You have read the suggestions in the CONTRIBUTING.md file https://github.com/Dokploy/dokploy/blob/canary/CONTRIBUTING.md#pull-request
• You have tested this PR in your local instance. If you have not tested it yet, please do so before submitting. This helps avoid wasting maintainers' time reviewing code that has not been verified by you.

Issues related (if applicable)

Screenshots (if applicable)

Greptile Summary

This PR updates @better-auth/sso and better-auth from version 1.4.18 to 1.5.0-beta.16, and includes several related changes to align with the new version:

• Renamed session_temp table to session via database migration
• Changed trustedProviders from static environment variable to dynamic database lookup via new getTrustedProviders() function
• Modified validateRequest logic to conditionally filter by activeOrganizationId and fall back to default organization when not set

Key changes:

• Database migration renames session table and updates constraints
• Dynamic SSO provider retrieval from database replaces static env var configuration
• Session validation now handles missing activeOrganizationId by selecting user's default/newest organization

Confidence Score: 3/5

• This PR has moderate risk due to session validation logic changes
• The dependency upgrade and table rename appear safe, but the modified validateRequest logic has a potential issue where activeOrganizationId is unconditionally overwritten even when member is null, which could cause session state inconsistencies
• Pay close attention to packages/server/src/lib/auth.ts - the session validation logic change needs verification

_{Last reviewed commit: 6cc646c}

[greptile-apps]

_{9 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

setting activeOrganizationId after retrieving the member creates inconsistency. The query searches for a member using session.session.activeOrganizationId (if present), but then unconditionally overwrites it with member?.organization.id || "". If member is null, this sets activeOrganizationId to an empty string, which could cause issues on subsequent requests.