Issue:
feat(connector): [Payme] Add Void flow to Payme

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [x] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
Add void to payme for cancelling transaction
Corresponding hotfix to https://github.com/juspay/hyperswitch/pull/3817
### Additional Changes

- [ ] This PR modifies the API contract
- [ ] 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`
-->


## Motivation and Context
<!--
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 it is 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)?
-->
Cannot be tested since cards are failing for Payme

## Checklist
<!-- Put an `x` in the boxes that apply -->

- [x] I formatted the code `cargo +nightly fmt --all`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed the 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:  feat(connector): [Bluesnap] Metadata to connector metadata mapping 
- Merged: 2024-01-30T09:29:47Z
- Files changed: 1 files
- Commits: 14 commits

Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [x] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
resolve [#3839](https://github.com/juspay/hyperswitch-cloud/issues/3839)
Metadata should be in 
{String : Value } type where Value is not an object. 
In case it is an object an Request Encoding error is thrown

##  Test Case?
Testing can
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** feat(connector): [Bluesnap] Metadata to connector metadata mapping  (#3331)
Co-authored-by: hyperswi
Files to modify:


**crates/router/src/connector/bluesnap/transformers.rs**
  Remove:
    - impl: impl TryFrom<BluesnapWebhookObjectResource> for serde_json::Value
  Add:
    - struct: pub::BluesnapMetadata
    - struct: pub::RequestMetadata