preserve dep optimization cache for each mode

[yuntian001]

Describe the bug

当vite dev 自定义模式mode（例如： vite --mode staging）启动时，总是会导致 optimized dependencies changed. reloading。

而直接用vite 或vite -m development启动时，没有这个问题。

用官方的vue ts包将 package.json 的scripts 的dev命令内容改为vite --mode staging 即可复现

Reproduction

https://github.com/vitejs/vite/tree/main/playground/vue

System Info

System:
    OS: Windows 10 10.0.17763
    CPU: (16) x64 Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
    Memory: 2.12 GB / 15.86 GB
  Binaries:
    Node: 16.15.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.13.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Internet Explorer: 11.0.17763.771

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

related code:

vite/packages/vite/src/node/optimizer/index.ts

Line 1041 in 1983cf4

mode: process.env.NODE_ENV || config.mode,

maybe related: #8878

[bluwy]

I suppose this could be useful too. Though it can be workaround by specifying process.env.NODE_ENV = 'development' in the Vite config so that dev can share the optimized deps, and in most case the optimized deps for different modes shouldn't be much different too 🤔 But when we optimize deps in builds in the future, I think this might be useful.