`vp staged` scan complete project after config change

### Description

I modified my `vite.config.ts` file to include more lint rules, after trying to commit, `vp staged` did report some new lint errors in the vite config file,
but did skip other files which are also effected. `vp lint` did show more error.
I would love to see `vp staged` to get more aligned with `vp lint`.

### Suggested solution

I suggest that after `vite.config.ts` file changes, the complete project should be linted and formatted (and maybe more).
There are possible more files that can change the projects' behavior, like the `package-lock.json`, which could update an internal lint/vite plugin.

### Alternative

_No response_

### Additional context

Coming from Discord:
https://discord.com/channels/1475973262193459293/1519815710354968626/1519815710354968626

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

Commencez par vite.config.ts et comparez les fichiers traités par vp staged avec ceux pris en charge par vp lint après une modification de configuration. Reproduisez le cas signalé, en incluant une modification de package-lock.json si elle est pertinente, puis vérifiez que les fichiers concernés du projet sont lintés et formatés de manière cohérente avec vp lint.

Rédigé par le modèle d'indexation à partir du texte de l'issue.