fix(cypress): use no_three_ds for Calida Bluecode wallet flow

[venkatakarthikm-maker]

The Bluecode wallet test hardcoded 'three_ds' for payment intent creation but Calida's confirm config specifies 'no_three_ds'. This auth type mismatch caused the confirm call to fail with 400, cascading to undefined nextActionUrl and 500 on sync.

Type of Change

• Bugfix

Description

Changed the hardcoded "three_ds" to "no_three_ds" in the Bluecode test context in 19-Wallet.cy.js to match the auth type declared in Calida.js. Calida's backend connector does not support 3DS — it's a pure wallet redirect flow (Bluecode QR scan).

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

Fixes #13139

How did you test it?

Ran Cypress specs 01, 02, 03, and 19 locally with CYPRESS_CONNECTOR=calida. All 5 Bluecode wallet tests pass:

1. create-payment-call-test ✅
2. payment_methods-call-test ✅
3. Confirm wallet redirect ✅
4. Handle wallet redirection ✅
5. Sync payment status ✅

Checklist

• I formatted the code
• I reviewed the submitted code

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
cypress-tests/cypress/e2e/spec/Payment/19-Wallet.cy.js	0% smaller

[XyneSpaces]

Code Review: Cypress Test Fix

Findings

[nit] This is a straightforward test configuration fix. Changing "three_ds" to "no_three_ds" for the Calida Bluecode wallet flow is correct if the connector doesn't support 3DS for this payment method.

[should-fix] Add a brief code comment explaining why no_three_ds is required for Calida Bluecode specifically. This helps future maintainers understand if this is:

1. A connector limitation
2. A test environment constraint
3. A specific flow requirement

Example:

// Calida Bluecode doesn't support 3DS authentication
"no_three_ds",

No blocking issues found.