Bug: chore(ci): `adyen` and `stripe` postman tests are failing



Multiple Test Cases have been failing on Postman,

- Adyen: <span style="color:red">88 Failures</span>
- Stripe: <span style="color:red">3 Failures</span>
  <img width="500" alt="Image" src="https://github.com/user-attachments/assets/522a3f3b-ef4d-450d-b584-8233d9008389" />
diff --git a/postman/collection-dir/stripe/PaymentConnectors/.meta.json b/postman/collection-dir/stripe/PaymentConnectors/.meta.json
index 6d68eeab4ab..c32be7223a6 100644
--- a/postman/collection-dir/stripe/PaymentConnectors/.meta.json
+++ b/postman/collection-dir/stripe/PaymentConnectors/.meta.json
@@ -5,7 +5,7 @@
     "Payment Connector - Update",
     "List Connectors by MID",
     "Payment Connector - Delete",
-    "Merchant Account - Delete",
-    "Delete API Key"
+    "Delete API Key",
+    "Merchant Account - Delete"
   ]
 }

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [x] Enhancement
- [x] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [x] CI/CD

## Description
<!-- Describe your changes in detail -->
Deleting API Key needs Merchant ID. So, deleting it after deleting the merchant itself yields a error message in the response which goes like `"API key not provided or invalid API key used"`, but, its solely because the Merchant ID used is not authenticated because the Merchant ID is already deleted.

### 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).
-->
The respective test case was failing in the Automated Tests Run.

## 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)?
-->
<img width="864" alt="image" src="https://github.com/user-attachments/assets/86d7ab3a-46b4-4476-804f-b200b3d67a05" />

The Remaining failures are because of outdated certificates and their keys. Once we update that it will be like the following

<img width="493" alt="image" src="https://github.com/user-attachments/assets/e45efb84-44d8-4f32-8d65-5ed7c1567a79" />


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [ ] 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
