feat(experience): handle secondary sign-up identifiers

[simeng-li]

Summary

This PR enhances the experience app to support the newly introduced secondaryIdentifiers settings in the sign-up flow.

Key changes

1. Preserved primary registration flow:

• Maintained the existing first-page registration form rendering logic
• Continues to use signUp.identifier as the primary sign-up method for the initial registration form

2. Additional identifiers collection:

• After initial registration form submission, users will be prompted to provide any additional required identifiers listed in the signUp.secondaryIdentifiers settings.
• Account creation and interaction submission are gated behind the completion of all required identifiers

3. Enhanced email/phone verification sign-in, account not exist error handling flow:

• Updated the verification code sign-in flow for email and phone
• Registration modal now appears when
  • The provided email/phone doesn't exist in Logto
  • Email/phone sign-up is enabled (either as a primary or secondary identifier)
  • User will be guided to provide other missing identifiers after the email/phone is submitted to complete the new account creation flow.

Other updates

1. Username registration flow refactor
   This PR also includes significant updates to the username registration flow, aligning it with the recent changes in sign-in experience settings:

• Previously, password setup was mandatory when username was set as a sign-up identifier. This restriction has been removed in the latest sign-in experience updates. See PR.
• Dynamic password setup routing at the experience app side:
  • Previously: Users were automatically redirected to the password setup page after submitting the username registration form.
  • New Implementation: Added conditional routing logic based on SIE settings
    • If password is required: User is redirected to set password page
    • If password is not required: Interaction is submitted directly
  • This change ensures the registration flow aligns with the configured sign-up settings

2. Revert the isDevFeaturesEnabled env variables reading logic update in PR

• The experience app does not yet support ESM in unit tests. import.meta will throw an error.
• Switch back to process.env till we migrate jest to vitest.

Testing

test locally

Checklist

• .changeset
• unit tests
• integration tests
• necessary TSDoc comments

[github-actions]

COMPARE TO master

Total Size Diff 📈 +4.98 KB

Diff by File

Name	Diff
packages/experience/src/components/IdentifierRegisterForm/use-register-with-username.ts	📈 +1.15 KB
packages/experience/src/constants/env.ts	📈 +149 Bytes
packages/experience/src/containers/VerificationCode/use-register-flow-code-verification.ts	📈 +283 Bytes
packages/experience/src/containers/VerificationCode/use-sign-in-flow-code-verification.ts	📈 +44 Bytes
packages/experience/src/hooks/use-sie.ts	📈 +3.88 KB
packages/experience/src/pages/RegisterPassword/index.tsx	📈 +38 Bytes
packages/experience/src/pages/VerificationCode/index.tsx	📈 +75 Bytes
packages/experience/vite.config.ts	📈 +464 Bytes