feat: add option to exclude global define and env replacement

[ygj6]

Description

Intent to fix vuejs/vitepress#419, but not completely resolved.

• Related clues:
  vite will automatically escape and replace the string form"process.env.NODE_ENV:" content!!! #3077
  Library Mode replaces "process.env.NODE_ENV" #3229
  Handling server-side/sensitive/runtime variables #3176

Ideally, the replacement of define and env can be turned off by specifying options, as in my test example.
I put forward this PR to stimulate discussion about whether the problems caused by string replacement should be fixed.
This is just one of my attempts, there should be other better ways to welcome you to point it out.
Thank you for your positive opinions.

Additional context

When I wrote the test example, I also found the error of define and pre-building, see also: #5570

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[kiaking]

@patak-dev Would it be possible to have this merged? Or maybe I might need a bit help on this issue. It's related to vuejs/vitepress#419 and it's breaking Vite 3 docs page as well (Env Variables and Modes page) 😅

[patak-dev]

@kiaking we need to discuss this with the team, but I don't think it is the best option. A user may want to use import.meta.env in their .md inside Vue components, and will have the same problem. Maybe we need some flag so Vite would ignore these, like \0process.env.
We have a few instances in the Vite docs, and we are now doing this as a workaround until we find a good path forward
https://github.com/vitejs/vite/blob/main/docs/guide/ssr.md?plain=1#L172

[kiaking]

Ah, I see good to see the workaround. OK, in that case we can skip this issue targeting VitePress alpha and just workaround with that technique for now. We can relax a bit then 👍

[bluwy]

I think we should find a more robust solution than a new config option to conditionally replace in some files. Maybe #11151 would help with this. IIRC there's also a builtin workaround for this in VitePress. Closing for now, but thanks for kicking off this option!