feat(router): add gateway_status_map CRUD APIs

[sai-harsha-vardhan]

Type of Change

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

Description

add gateway_status_map CRUD APIs

Additional Changes

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

Motivation and Context

How did you test it?

Tested Manually

1. GSM Create
   CURL

 curl --location --request POST 'https://sandbox.hyperswitch.io/gsm' \
--header 'api-key: {ADMIN_API_KEY}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "connector": "stripe",
    "flow": "Authorize",
    "sub_flow": "sub_flow",
    "code": "incorrect_cvc",
    "message": "incorrect_cvc",
    "status": "failure",
    "decision": "retry",
    "step_up_possible": true
}' 

2. GSM Update
   CURL

curl --location --request POST 'https://sandbox.hyperswitch.io/gsm/update' \
--header 'api-key: {ADMIN_API_KEY}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "connector": "stripe",
    "flow": "Authorize",
    "sub_flow": "sub_flow",
    "code": "incorrect_cvc",
    "message": "incorrect_cvc",
    "decision": "do_default"
}' 

3. GSM Retrieve
   CURL

curl --location --request POST 'https://sandbox.hyperswitch.io/gsm/get' \
--header 'api-key: {ADMIN_API_KEY}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "connector": "stripe",
    "flow": "Authorize",
    "sub_flow": "sub_flow",
    "code": "incorrect_cvc",
    "message": "incorrect_cvc"
}' 

4. GSM Delete
   CURL

curl --location --request POST 'https://sandbox.hyperswitch.io/gsm/delete' \
--header 'api-key: {ADMIN_API_KEY}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "connector": "stripe",
    "flow": "Authorize",
    "sub_flow": "sub_flow",
    "code": "incorrect_cvc",
    "message": "incorrect_cvc"
}'

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

[Narayanbhat166]

the endpoints and http methods do not match, ideally get should go with the GET http method, same for the rest

[sai-harsha-vardhan]

For all CRUD APIs we need payload with connector, flow, sub_flow, code and message fields

[SanchithHegde]

The GET endpoint can use query parameters if the values are all single values (and not a list of values).

[Narayanbhat166]

In order to make it easier to use the gsm apis, a gsm list endpoint will be a good addition. This endpoint can have filters for connector, flow_type etc. Also the update endpoint should not allow the primary key fields to be updated and instead allow only the actions ( step_up, retry_action etc ) to be updated. Each gsm can have a unique identifier gsm_abcd which will act as a primary key to update / delete the gsm entry.

This can be added as a good first issue.

[SanchithHegde]

Other than that, looks good to me!

[SanchithHegde]

The GET endpoint can use query parameters if the values are all single values (and not a list of values).

[likhinbopanna]

@sai-harsha-vardhan Can you add the cURL request?

[Narayanbhat166]

are the errors due to changes in this PR?

[sai-harsha-vardhan]

are the errors due to changes in this PR?

@Narayanbhat166 This is due to APIEventMetrics which are added recently, fixing it!