feat(router): add support for cost based debit routing

[ShankarSinghC]

Type of Change

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

Description

This pull request introduces a new configuration for debit routing, including fees for fraud checks, network processing, and interchange. It also adds methods to calculate these fees and integrates them into the existing system.

For every payment that occurs, there are three fees associated with the network:

1. Network Fee
   Every network has its own network fee structure, which typically includes both a percentage (% of the amount) and a fixed fee. For each payment, the respective network will charge a specific percentage and a fixed amount.

2. Interchange Fee
   If the bank is a regulated bank, it can charge only a specified percentage and fixed amount for the transaction. If the bank is not a regulated bank, then, similar to the network fee, the bank can charge different amounts depending on the network.

3. Fraud Check Fee
   When a bank is regulated under an exemption for fraud checks, it may charge an additional fee only if a fraud check is conducted.

When a payment is being performed all this factors should be taken in consideration and a network should be chosen according to merchant's configuration

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?

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/router/src/core/co_badged_cards_info.rs	1% smaller
config/config.example.toml	Unsupported file format
config/deployments/integration_test.toml	Unsupported file format
config/deployments/production.toml	Unsupported file format
config/deployments/sandbox.toml	Unsupported file format
config/development.toml	Unsupported file format
config/docker_compose.toml	Unsupported file format
crates/common_enums/src/enums.rs	0% smaller
crates/diesel_models/src/co_badged_cards_info.rs	0% smaller
crates/router/src/configs/secrets_transformers.rs	0% smaller
crates/router/src/configs/settings.rs	0% smaller
loadtest/config/development.toml	Unsupported file format

[vspecky]

How many category codes can there be? If it's more than 20, we should consider making this a HashMap instead.