Bug: [REFACTOR] reduce duplicate code in config in cypress



- too much chaos and confusion
- boiler plate and duplicate code
- move memory cache test out of payments and make it a separate service
## 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:
- `cypress-tests` folder structure to reduce confusion and chaos in within `e2e` directory
	- previous:
		```sh
		.
		└── cypress
		    ├── e2e
		    │   ├── PaymentMethodListTest
		    │   ├── PaymentMethodListUtils
		    │   ├── PaymentTest
		    │   ├── PaymentUtils
		    │   ├── PayoutTest
		    │   ├── PayoutUtils
		    │   ├── RoutingTest
		    │   └── RoutingUtils
		    ├── fixtures
		    ├── support
		    └── utils
		```
	
	- present:
		```sh
		.
		└── cypress
		    ├── e2e
		    │   ├── configs
		    │   │   ├── Payment
		    │   │   ├── PaymentMethodList
		    │   │   ├── Payout
		    │   │   └── Routing
		    │   └── spec
		    │       ├── Misc <- memory cache tests have been moved here
		    │       ├── Payment
		    │       ├── PaymentMethodList
		    │       ├── Payout
		    │       └── Routing
		    ├── fixtures
		    ├── support
		    └── utils
		```

- reduce / remove duplicate commands in memory cache (config calls) by unifying them
	- #6961 introduces the memory cache test, but does not aim at optimising things. this pr is intended to address that
	- additionally, memory cache test have been moved out of `payments` service to `misc` just so that, tests that are independent of business profile, mca, merchant account can be added here in the future
- new command addition to miscellaneous tests: `npm run cypress:misc`
- slight security improvement by forcing the api key to expire within `24` hours

closes #6993

documentation will be updated later

### 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).
-->

Too many boiler plates, too many useless code

## 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)?
-->

```sh
# executed below command to cherry-pick cookie changes just so that userlogin work
git cherry-pick -n ..fix-cookie-cypress

# started cypress against stripe
CYPRESS_CONNECTOR=stripe npm run cypress
```

stripe:
<img width="556" alt="image" src="https://github.com/user-attachments/assets/df8c443f-d0ba-4f8b-ac65-a68ad5f7c89e" />

memory cache:
<img width="554" alt="image" src="https://github.com/user-attachments/assets/10545633-7691-4841-831a-38f04ca9a91a" />

health check:
<img width="467" alt="image" src="https://github.com/user-attachments/assets/3e14bd10-4f05-42c9-84f9-c925beae15e3" />


ci:

![image](https://github.com/user-attachments/assets/d48820dc-a102-4475-867e-4783c0430272)


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

- [x] I formatted the code `npm run format`
- [x] I addressed lints thrown by `npm run lint`
- [x] I reviewed the submitted code
- [ ] I added unit tests for my changes where possible
