feat: enable onboarding-v3 feature flag

[sean-brydon]

What does this PR do?

Adds a database migration to enable the onboarding-v3 feature flag globally. The feature flag was previously added in migration 20251005102651_add_onboarding_v3_feature_flag with enabled=false. This migration updates it to enabled=true.

Also updates the onboarding E2E tests to conditionally run either the V1 or V3 flow based on the feature flag status.

Summary of Changes

Database Migration:

• Enables onboarding-v3 feature flag globally

E2E Test Updates:

• Renamed testOnboarding to testOnboardingV1 with feature flag check to skip when V3 is enabled
• Added new testOnboardingV3 function that tests the new onboarding flow (plan selection → personal settings → calendar)
• V3 tests skip when the feature flag is disabled, V1 tests skip when enabled
• Both test suites run for GOOGLE, CAL, and SAML identity providers

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A - no documentation changes needed.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

Database Migration:

1. After running migrations (yarn workspace @calcom/prisma db-migrate), check the Feature table to confirm onboarding-v3 has enabled=true
2. Verify the onboarding v3 flow is active for users

E2E Tests:

1. With onboarding-v3 feature flag enabled - V3 tests should run, V1 tests should skip
2. Verify the V3 flow tests correctly navigate through: plan selection → personal settings → calendar → event-types

Human Review Checklist

• Confirm enabling onboarding-v3 globally is the intended behavior
• Verify there are no downstream effects that need to be considered before enabling this feature
• Verify the V3 test selectors (page.getByText("Personal"), page.getByLabel("Your name"), page.getByRole("button", { name: "Skip for now" })) match the actual UI elements - these were inferred from source code review
• Note: V3 onboarding components don't have data-testid attributes, so tests rely on text content/ARIA labels which may be more fragile

---

Link to Devin run: https://app.devin.ai/sessions/0bea3e60c75c498a8708733551122a52
Requested by: @sean-brydon

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[cubic-dev-ai]

No issues found across 1 file

[github-actions]

E2E results are ready!

• Workflow #99426.1 latest results

[keithwillcode]

Tests are consistently failing @sean-brydon