Issue:
Bug: [BUG] API Reference documentation broken



### Bug Description

API reference is broken for following endpoints:
- `API Key - Create`
- `API Key - Revoke`
- `Routing - Retrieve`
- `Routing - Activate Config`

### Expected Behavior

<img width="1514" alt="image" src="https://github.com/user-attachments/assets/139a8e53-1d10-4e60-98c4-a4cb569f3d22">


### Actual Behavior

<img width="1514" alt="image" src="https://github.com/user-attachments/assets/f89e07c1-94a3-4e95-8a19-1c3495138704">


### Steps To Reproduce

Go to https://api-reference.hyperswitch.io/api-reference/api-key/api-key--create



### Context For The Bug

_No response_

### Environment

Web

### Have you spent some time checking if this bug has been raised before?

- [X] I checked and didn't find a 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?

Yes, I am willing to submit a PR!

Pull request description:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [x] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [x] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
Fixed broken API reference for the following endpoints:

- `API Key - Create`
- `API Key - Revoke`
- `Routing - Retrieve`
- `Routing - Activate Config`

### 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).
-->


## 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)?
-->


## 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


Testing:

Patch: