Issue:
ci(postman): refactor NMI postman collection

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD

## Description
<!-- Describe your changes in detail -->
This PR aims at refactoring NMI collection by bringing it back to life. Added more flows to look after regressions.

Closes #3734

### 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).
-->

We need to check for regressions.

## 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)?
-->

Ran the collection:

<img width="980" alt="image" src="https://github.com/juspay/hyperswitch/assets/69745008/9aaad0eb-a4d7-4735-9d8c-303d323fc915">

There is a bug in NMI connector which needs to be addressed.  

Created a separate collection to reproduce it.

## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] I formatted the code `cargo +nightly fmt --all`
- [ ] 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: refactor(test_utils): use json to run collection and add run time edit
- Merged: 2024-03-04T08:13:36Z
- Files changed: 30 files
- Commits: 30 commits

Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [ ] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD

## Description
<!-- Describe your changes in detail -->

This PR refactors test_utils crate's `newman_runner` to support dynamic values through postman variables.

The main issue with `newman-dir` is that in order to export the collection, the variables must be of type string (Example: Variable 
</think>

To implement this, you'll need to modify:


**Detailed Implementation:**


**Commit 1:** refactor(test_utils): use json to run collection and add run time edit (#3807)
Co-authored-by: hyper
Files to modify:


**crates/test_utils/src/main.rs**
  Modify existing code

**crates/test_utils/src/newman_runner.rs**
  Add:
    - function: private::get_collection_path
    - function: pub::check_connector_for_dynamic_amount
    - function: pub::remove_quotes_for_integer_values