npm v7+ strict peer dependency resolution fails due to i18next / react-i18next mismatch

### Describe the bug.

On npm v7+ (strict peer dependency resolution), a fresh `npm install` fails with an `ERESOLVE unable to resolve dependency tree` error.

This appears to be caused by a peer dependency version mismatch between `i18next`, `react-i18next`, and `next-i18next` under npm v7+ strict resolution.

### Expected behavior

`npm install` should complete successfully on npm v7+ without requiring `--legacy-peer-deps` or manual dependency alignment.

### Screenshots

npm v10 failing during clean install due to dependency resolution error.

### How to Reproduce

1. Use npm v7+ (tested with npm v10)
2. Clone the repository
3. Run `npm install`

### 🖥️ Device Information [optional]

- Operating System (OS):Ubuntu 22.04 (WSL on Windows)
- Browser: N/A
- Browser Version: N/A

### 👀 Have you checked for similar open issues?

- [x] I checked and didn't find similar issue

### 🏢 Have you read the Contributing Guidelines?

- [x] I have read the [Contributing Guidelines](https://github.com/asyncapi/.github/blob/master/CONTRIBUTING.md)

### Are you willing to work on this issue ?

Yes I am willing to submit a PR!

Start by reproducing the reported failure with npm v7+ or npm v10 using a clean checkout and `npm install`; inspect the repository's dependency declarations to identify the i18next, react-i18next, and next-i18next mismatch. Done means a fresh install completes without `--legacy-peer-deps` or manual dependency alignment.

Written by the indexing model from the issue text.