feat(core): Changed frm_config format type in merchant_connector_account and added frm_message in payments response

[rishavkar]

Type of Change

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

Description

These changes are done for FRM related improvements:

• add frm_message to PaymentData...changed PaymentsResponse struct and added frm_message
• changed type of payment_method_type in FrmPaymentMethodType
• changed type of FrmConfig to new type...made relevant changes....also changes api contract and db schema
• Make email service optional for frm
• Make email feature optional in AppStateInfo

Additional Changes

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

changes in DB schema to change type of frm_configs:

ALTER TABLE merchant_connector_account 
ALTER COLUMN frm_configs TYPE jsonb[]
USING ARRAY[frm_configs]::jsonb[];

changed the API contract for merchant_connector_account.... frm_configs field changed to :

#[schema(example = json!([{
        "gateway": "stripe",
        "payment_methods": [{
            "payment_method": "card",
            "payment_method_types": [{
                    "payment_method_type": "credit",
                    "card_networks": [
                        "Visa"
                    ],
                    "flow": "pre",
                    "action": "cancel_txn"
                },
                {
                    "payment_method_type": "debit",
                    "card_networks": [
                        "Visa"
                    ],
                    "flow": "pre"
                }
            ]
        }]
    }]))]
    pub frm_configs: Option<Vec<FrmConfigs>>,

Motivation and Context

Needed to change these, so that they can be consumed by our FRM module.

How did you test it?

Checklist

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

[jarnura]

We need to move away from auto increment ids for any distributed storage related approaches. And migration without downtime with auto-increment id's also hard. So don't need this field