Dash 4249 setup flow 3ds

[Devlaird]

📝 Description

Jira ticket: https://fatzebra.atlassian.net/browse/DASH-4249?search_id=3590e8d5-56b4-47e3-a26b-e534cbeb9967

Details of change

Here is the sequence diagram:
ThreeDSecureSetup.pdf

Successful setup

We don't need to emit successful setup as its an initial step

Unsuccessful setup

if gateway is down/jabberwocky is down or if cybersource throws a fit and doesn't respond.

This is unlikely, but handled nonetheless

Change Rollback Plan

• Roll forward (this path is feature flagged under: new_threeds_flow

Change Checklist

The following must be reviewed and signed off by the creator of the PR. To sign off review and check each

🔑 Security

• Security of any environment is not reduced by this change.
• All existing security controls remain in place or have been replaced with equal or stronger controls.

Testing of Changes

• Testing results have been verified as complete and covering all aspects of the change.
• Evidence of testing attached
• Security scans are passing
• No package vulnerabilities introduced

🔎 Quality assurance

• Reviewed this PR myself
• Automated tests are required and included
• Security controls have been reviewed
• Changes are Blue-Green friendly

[snyk-io-au]

⚠️ Snyk checks are incomplete.

Status	Scanner	Critical	High	Medium	Low	Total (0)
⚠️	Open Source Security	0	0	0	0	See details
⚠️	Licenses	0	0	0	0	See details
✅	Code Security	0	0	0	0	0 issues

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

[Devlaird]

this is a general failure bridge event - rename from: "SETUP_THREE_D_SECURE_FAILURE_RESPONSE" ->
"THREE_D_SECURE_FAILURE_RESPONSE" and fzi.3ds_stp_fail -> fzi.3ds_fail