Issue:
feat(single_use): add extra fields in `Mandate` table and `MandateData` [Blocked on #61]

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates

## Description
This PR adds single use mandate support and a 2 new fields to the mandate table (i.e. singe_use_amount, single_use_currency)
<!-- Describe your changes in detail -->


### Additional Changes

- [x] This PR modifies the database schema
- [ ] 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`
-->
The change includes the following files.
- migrations/2022-12-05-090521_single_use_mandate_fields/up.sql
- migrations/2022-12-05-090521_single_use_mandate_fields/down.sql


## Motivation and Context
Here, the intension is adding a new Validation feature in PaymentsCore, for that reason following are the steps that the change is broken down to.

1. Create new types for the change #45 
2. Introduce the Flow and Connector Integration #47 
3. Add Stripe POC #50
4. Introduce the new operation and all the related components in the payments core #53 + #61 
5. Changing the `MandateData` type
6. Move the mandate related behaviour to domain
<!--
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).
-->


## 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)?
-->


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [x] I formatted the code `cargo +nightly fmt`
- [x] I addressed lints thrown by `cargo clippy`
- [x] 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: fix(payout): use get_string_repr for formatting payout IDs
- Merged: 2025-07-05T15:11:29Z
- Files changed: 10 files
- Commits: 2 commits

Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
This PR fixes the bug report - https://github.com/juspay/hyperswitch/issues/8392#issuecomment-3032692625

Introduces below changes
- Use `get_string_repr` for formatting payoutIDs which were using default formatter
- Update connector configs for `adyenplatform` (WASM)
- Update pa
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** fix(payout): use get_string_repr for formatting payout IDs (#8547)
Co-authored-by: hyperswitch-bot[b
Files to modify:


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