fix(TU-18127): Replace __dangerous-disable-submissions with enable-sandbox=true

[tom-ridsdale]

Summary

https://typeform.atlassian.net/browse/TU-18127

Separate sandbox mode behaviour from submission-disabled mode by introducing a distinct enable-sandbox query parameter.

Problem

Previously, enableSandbox: true in the embed SDK would pass __dangerous-disable-submissions=true to the renderer, causing sandbox mode and submission-disabled mode to be treated identically. This prevents redirects from working in sandboxed embeds.

Solution

Pass enable-sandbox=true instead of __dangerous-disable-submissions=true when enableSandbox is set, allowing the renderer to distinguish between the two flows.

[tf-security]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Licenses	0	0	0	0	0 issues
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[typeform-ops-gha]

[BOT] Preview available with hash d60f07879a50b693607024fa2e5ebd4358433489 here.

[sonarqubecloud]

Quality Gate passed

Issues
65 New issues
0 Accepted issues

Measures
1 Security Hotspot
76.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gitstream-cm]

🥷 Code experts: No results found

No code experts were identified for the files in this pull request based on git blame analysis.

This may occur when:

• Files are new or have limited commit history
• Git authors aren't mapped to current team members
• Analysis thresholds need adjustment

If you expected to see expert suggestions, consider:

• Reviewing your config.user_mapping settings

• Adjusting the gt/lt parameters in your action

• Verifying files have sufficient commit history

To learn more about /:\gitStream - Visit our Docs