fix(frm): added fraud_check_last_step field in fraud_check table to support 3DS transaction in frm

[jagan-jaya]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Currently, frm module dosent work for 3ds flow.
It is because, payments operation core is called multiple times in the same request, and so is pre and post frm.
This creates duplicate entries, and also creates discrepencies.
To fix this, we are adding a field fraud_check_last_step in the fraud check table. This is to indicate the last step executed in the frm flow, and we will restrict few actions based on the last_step.

Eg 1: if the last_step is processing, then we can do checkout or sale nothing else
Eg 2: if the last_step is checkout_or_sale, then we can do transaction or refund or fullfillment
Eg 3: if the last_step is transaction_or_record_refund, then we can either only do fullfillment

Additional Changes

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

• is_terminated is added to table fraud_check.

Motivation and Context

How did you test it?

• do a 3ds flow, with frm.
• for both pre and post flow, at the end of the flow, the is_terminated field should be set to true in the fraud_check table.
• for pre flow, signifyd should be called twice(once before and once after transaction), not 4 times.
• for post flow, it should be called only hitting the redirection link, and completing the authentication, i.e., only after the transaction is complete,i.e., frm should be called just once, not twice.

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable