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

Start with vite.config.ts and compare which files vp staged processes with those handled by vp lint after a configuration change. Reproduce the reported case, including a package-lock.json change if relevant, then verify that affected project files are linted and formatted consistently with vp lint.

Written by the indexing model from the issue text.