feat(payouts): extend routing capabilities to payout operation

[kashif-m]

Type of Change

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

Description

Explained in issue #1845

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 locally using Postman collection for payouts routing - https://postman.co/workspace/My-Workspace~2b563e0d-bad3-420f-8c0b-0fd5b278a4fe/collection/9906252-a04b7f48-7689-4eac-8a84-9b5c5af8ba50?action=share&creator=9906252

Steps for testing
Assuming merchant account and payout connectors are created.

All these steps can be found in the linked postman collection.

1. Add a volume split rule
2. Activate this rule
3. Create multiple payouts (and check the connectors being evaluated in the response)
4. Deactivate this rule
5. Add an advanced split rule
6. Create multiple payouts (and check the connectors being evaluated in the response))
7. Activate this rule
8. Deactivate this rule

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

[prajjwalkumar17]

Hey @kashif-m
Can we first of all check on the failing MSRV tests and probably once regenerate the Open-api spec file.

[prajjwalkumar17]

Needs a mandatory review from @vspecky as the changes are intersecting most of the euclidian family crates.

cc: @vspecky @tinu-hareesswar @Gnanasundari24