fix: ensure define overrides import.meta in build

[bluwy]

Description

fix #8865

Additional context

The reason for the code change is explained in #8865 (comment)

In short, define should take precedence over import.meta.env.* when both have the same key.

---

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.

[netlify]

✅ Deploy Preview for vite-docs-main canceled.

Name	Link
🔨 Latest commit	836040c
🔍 Latest deploy log	https://app.netlify.com/sites/vite-docs-main/deploys/62c1386a2402a30008013b06

[patak-dev]

Approved before seeing the failing test, but the change LGTM

[bluwy]

My bad. It looks like there's a special case in plugin-legacy where define: { 'import.meta.env.LEGACY' }, but this env isn't in the .env file, which I've only tested. So previously import.meta.env. got replaced instead, causing the error. Moving them after define returns to the expect behaviour.

[caocos]

Good，thank you! ^_^

If print all envs, can also display types, it's better

console.log(import.meta.env)