Issue:
Bug: add  `ApiKeyAuth` support for `upsert_connector_agnostic_mandate_config`



Add support for api-key auth for pg_agnotic config api enpoint. As it is required by merchant to enable the config until the dashboard changes are done.

Pull request description:
## 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 support for api-key auth for `pg_agnotic` config api enpoint.

### Additional Changes

- [x] 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)?
-->
```
curl --location 'http://localhost:8080/routing/business_profile/{{business_profile_id}}/configs/pg_agnostic_mit' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: api-key' \
--data '{
    "enabled": true
}'
```
![image](https://github.com/juspay/hyperswitch/assets/83439957/67c554cf-4f7a-4b0a-bd49-26ebc1e43067)

## 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


Testing:

```
curl --location 'http://localhost:8080/routing/business_profile/{{business_profile_id}}/configs/pg_agnostic_mit' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'api-key: api-key' \
--data '{
    "enabled": true
}'
```
![image](https://github.com/juspay/hyperswitch/assets/83439957/67c554cf-4f7a-4b0a-bd49-26ebc1e43067)

Patch:
diff --git a/crates/router/src/routes/routing.rs b/crates/router/src/routes/routing.rs
index 28d65f66a82..5d8330a05b4 100644
--- a/crates/router/src/routes/routing.rs
+++ b/crates/router/src/routes/routing.rs
@@ -591,14 +591,11 @@ pub async fn upsert_connector_agnostic_mandate_config(
                 mandate_config,
             ))
         },
-        #[cfg(not(feature = "release"))]
         auth::auth_type(
             &auth::ApiKeyAuth,
             &auth::JWTAuth(Permission::RoutingWrite),
             req.headers(),
         ),
-        #[cfg(feature = "release")]
-        &auth::JWTAuth(Permission::RoutingWrite),
         api_locking::LockAction::NotApplicable,
     ))
     .await