Warn on certain other tooling config files

### Description

Currently Vite+ migrates the following first-party tool configurations automatically:

- Vite (`vite.config.ts`)
- Vitest (`vitest.config.ts`)
- tsdown (`tsdown.config.ts`)
- Oxlint (`.oxlintrc.json`)
- Oxfmt (`.oxfmtrc.json`)

As well as the following third-party tool configurations:

- ESLint (via `@oxlint/migrate`)
- Prettier (via `oxfmt --migrate` flow)
- tsup (via `tsdown-migrate`)

However, this still leaves certain tools unmigrated, which may have a Vite+-native replacement.

### Suggested solution

The following tools, if they and their config files are detected in the current project, will trigger a warning during `vp migrate`, pointing to each respective tool's instructions for migrating where possible:

- Jest / `vite-jest` -> Vitest
- `vite-jest` is 5 years old so it's probably going to be harder to migrate for most people.
- Rolldown -> Vite or tsdown
- Most users of Rolldown directly are likely looking for something like tsdown. The Vite mention is for if the user is a frontend library developer, in which case Vite(+)'s Library Mode probably makes more sense.
- Rollup -> Rolldown or tsdown
- I do not believe there is a direct Rollup -> tsdown migration guide, it probably makes sense to point to Rolldown's instead, but then it runs into the above condition of migrating off of direct Rolldown usage.
- Biome? -> oxlint/oxfmt
- This one is a bit of a stretch considering their current plugins API is different on a fundamental level, not to mention their parser being different, so I'm probably going to drop this in the final implementation.

### Alternative

Not letting the user know. This means the user might be using an entirely different set of tools which may behave differently, partially defeating the point of the unified toolchain vision of Vite+.

### Additional context

I'm thinking of working on this, it's been a thing on my mind for a couple of months now.

### Validations

- [x] Read the [Contributing Guidelines](https://github.com/voidzero-dev/vite-plus/blob/main/CONTRIBUTING.md).
- [x] Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
- [x] Check that there isn't already an issue requesting the same feature.

Start at the `vp migrate` entry point and inspect how existing Vite+, Vitest, tsdown, Oxlint, and Oxfmt configuration files are detected. Review the listed Jest, Rolldown, Rollup, and possible Biome migration guidance. Done means detected configurations produce the appropriate migration warnings and point users to the relevant instructions.

Vom Indexierungsmodell aus dem Issue-Text verfasst.