fix(@angular/build): isolate Vite cache per build configuration in dev server

[maruthang]

Summary

• Running two ng serve instances for the same project with different configurations (e.g., different locales) caused "504 Outdated Optimize Dep" errors
• Both instances shared the same Vite optimizer cache directory (<cache>/<project>/vite), so when one instance updated the cache, the other detected stale metadata
• The fix includes the build configuration name in the cache path (<cache>/<project>/vite/<configuration>), isolating each instance's cache

Closes #31700

Test plan

• Run two ng serve instances with different configurations concurrently — no 504 errors
• Single ng serve instance still works correctly
• Cache directory is properly created with configuration suffix

[gemini-code-assist]

Code Review

This pull request updates the Vite dev server configuration to include the build configuration in the cache path. This change prevents potential conflicts when running multiple dev server instances with different configurations. I have no further feedback to provide.

[alan-agius4]

Woah, looks like you've opened a lot issues/PRs recently. While we appreciate contributions from the community, triaging and reviewing a large influx of content in a short time period takes time away from other ongoing projects. As a result, we're closing these issues/PRs to maintain the team's focus.

Note that this is not necessarily a rejection of the goals or direction of any of these contributions in particular, so much as a reflection of the team's current capacity and priorities.

You are welcome to open a smaller subset of issues/PRs focused on the most important and impactful contributions and we will do our best to prioritize a response as soon as possible.

Community contributors should limit themselves to no more than 3 open PRs at a single time.