Issue:
[FEATURE] add domain type for client secret 

### Feature Description

Create domain type for client secret

### Possible Implementation

Make type `ClietSecret(String)` and use it wherever applicable

### Have you spent some time to check if this feature request has been raised before?

- [X] I checked and didn't find similar issue

### Have you read the Contributing Guidelines?

- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

No, but I'm happy to collaborate on a PR with someone else

Resolution:
<think>
PR Context:
- Title: fix(payments): fix client secret parsing
- Merged: 2023-06-21T07:20:53Z
- Files changed: 1 files
- Commits: 6 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
<!-- Describe your changes in detail -->

Client secret parsing logic could create bugs changed it to avoid them. 

Ideally , it will be good to pass payment_id everywhere and ask for payment_id in the request wherever applicable and never extract payment_id from client_secret. To
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** fix(payments): fix client secret parsing (#1358)
Files to modify:


**crates/router/src/core/payments/helpers.rs**
  Add:
    - function: private::test_client_secret_parse
    - mod: private::test