Preserve OAuth authorize URL through sign-in redirect

[UsamaSadiq]

Description

When an unauthenticated user hits /authorize during MCP OAuth (e.g. from Claude.ai), PageChangeEffect discards the full OAuth URL (client_id, redirect_uri, state, code_challenge) and redirects to /sign-in-up. After login the user lands on the homepage instead of returning to the OAuth consent page.

Fix: encode the full /authorize?... URL as returnToPath so the existing post-login redirect mechanism routes back to the consent flow with all OAuth params intact.

Testing

1. Add Twenty MCP connector in Claude.ai: https://twenty.moneta.askii.ai/mcp
2. When not logged into Twenty, the OAuth flow should redirect to sign-in, then after login return to the authorize consent page
3. After clicking "Authorize", the browser should redirect back to Claude.ai (not the Twenty homepage)

[github-actions]

	Fails
🚫	node failed.

Log

Details

�[31mError: �[39m SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
    at JSON.parse (<anonymous>)
�[90m    at parseJSONFromBytes (node:internal/deps/undici/undici:4387:19)�[39m
�[90m    at successSteps (node:internal/deps/undici/undici:7041:27)�[39m
�[90m    at readAllBytes (node:internal/deps/undici/undici:5958:13)�[39m
�[90m    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)�[39m
danger-results://tmp/danger-results-0793c22f.json

Generated by 🚫 dangerJS against b90aa0e