Use oxlint plugin to validate and auto-fix IDE configuration issues

### Description

Following the discussions in issue #826, it was noted that misconfigurations in the Zed IDE (e.g., an incorrect configPath in oxfmt settings) do not provide any feedback, making it difficult to diagnose why the tool is not working as expected.

Once the implementation of #1408 (oxlint plugin) is complete, we will use this feature to detect and automatically fix issues within .zed/settings.json and .vscode/settings.json.

- Add an oxlint plugin rule to validate IDE configuration files against schemas generated by vp create or vp migrate.
- Support the --fix option to enable automatic corrections for safe, known configuration errors, such as aligning configPath with ./vite.config.ts.
- Integrate this into vp check --fix so that these corrections are performed as part of the regular development workflow.

### Suggested solution

Implement an oxlint plugin rule (e.g. `vite-plus/ide-config`) that reads the Vite+ config and checks IDE config files for known misconfigurations. The rule runs as part of `vp check`, and with `--fix` it rewrites the config to match what `vp create`/`vp migrate` would generate.

### Alternative

A separate `vp config check` subcommand could validate and repair IDE config files without depending on the oxlint plugin infrastructure. However, integrating with `vp check --fix` keeps the workflow unified and avoids adding a new command.

### Additional context

_No response_

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