refactor(gsm): add error_category and error_sub_category columns to gsm table

[Chethan-rao]

Type of Change

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

Description

This PR adds error_category and error_sub_category columns to gsm table which is an enum in application. These could be used to take multiple decisions in future but currently these are required for elimination routing in which these categories will serve as bucket name.
Additionally it fixes the last_modified column not being updated in gsm table during /update

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?

Added 2 new columns to GSM tables. (error_category, error_sub_category)

curl --location 'https://localhost:8080/gsm' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: test_admin' \
--data '{
  "connector": "stripe",
  "flow" : "flow1",
  "sub_flow": "sub_flow",
  "code": "incorrect_cvc",
  "status": "status1",
  "decision": "retry",
  "message": "xyz",
  "step_up_possible": false,
  "error_category": "technical_error_with_processor",
  "error_sub_category": "server_error"
}'

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

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
crates/diesel_models/src/gsm.rs	27% smaller
crates/openapi/src/openapi.rs	15% smaller
crates/openapi/src/openapi_v2.rs	15% smaller
api-reference-v2/openapi_spec.json	0% smaller
api-reference/openapi_spec.json	0% smaller
crates/api_models/src/gsm.rs	0% smaller
crates/common_enums/src/enums.rs	0% smaller
crates/diesel_models/src/schema.rs	0% smaller
crates/diesel_models/src/schema_v2.rs	0% smaller
crates/router/src/core/gsm.rs	0% smaller
crates/router/src/types/transformers.rs	0% smaller
migrations/2024-11-24-104438_add_error_category_col_to_gsm/down.sql	Unsupported file format
migrations/2024-11-24-104438_add_error_category_col_to_gsm/up.sql	Unsupported file format

[sai-harsha-vardhan]

We already have ConnectorErrorType which is used for different purpose in auto retries flow, and has the following values
UserError, BusinessError, TechnicalError, UnknownError

Should we follow the same here? @Chethan-rao
cc: @jarnura