Issue:
added field frm_configs to MerchantConnectorAccount

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates

## Description
<!-- Describe your changes in detail -->
We need to accept frm_configs from the dashboard. So needed to do development for accepting new fields for endpoint: `/account/:account_id/connectors`

### Additional Changes

- [x] This PR modifies the database schema : 
                    `ALTER TABLE "merchant_connector_account" ADD COLUMN frm_configs jsonb;`
- [ ] This PR modifies application configuration/environment variables

<!-- 
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless its an obvious bug or documentation fix
that will have little conversation).
-->
It a new feature...we are going to integrate FRM services into hyperswitch, for which we required additional fields for create connector request. 
This PR will accept frm_configs field for create connector request, and accordingly persist in the db.

## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->
Following are the steps:
- Adding an extra field to the request body, to existing curl.
- Getting 200 and Expecting this same body in response.
  ```
"frm_configs" : {
      "frm_enabled_pms" : ["card"],
      "frm_enabled_pm_types" : ["credit"],
      "frm_enabled_gateways" : ["stripe"],
      "frm_action": "cancel_txn",
      "frm_preferred_flow_type" : "pre"
  }
```


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] 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](/CHANGELOG.md) entry if applicable


Resolution:
<think>
PR Context:
- Title: Revert "added field frm_configs to MerchantConnectorAccount"
- Merged: 2023-04-10T13:21:18Z
- Files changed: 10 files
- Commits: 1 commits

Implementation approach:
Reverts juspay/hyperswitch#831

The frm_configs handled as a mandatory field in flows.
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** Revert "added field frm_configs to MerchantConnectorAccount" (#848)
Files to modify:


**crates/api_models/src/admin.rs**
  Remove:
    - struct: pub::FrmConfigs

**crates/api_models/src/enums.rs**
  Remove:
    - enum: pub::FrmAction
    - enum: pub::FrmPreferredFlowTypes

**crates/router/src/core/admin.rs**
  Modify existing code

**crates/router/src/core/payments/flows/authorize_flow.rs**
  Modify existing code

**crates/router/src/db/merchant_connector_account.rs**
  Modify existing code

**crates/router/src/types/transformers.rs**
  Modify existing code

**crates/storage_models/src/merchant_connector_account.rs**
  Modify existing code

**crates/storage_models/src/schema.rs**
  Modify existing code