chore: revert "fix(ssr): hoist import statements to the top (#12274)"

[sapphi-red]

Description

revert #12274

#12274 seems to break nuxt, plugin-react ecosystem-ci.
This PR fixes the other half part of the fails.

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sapphi-red]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI: Open

suite	result
astro	❌ failure
histoire	❌ failure
iles	✅ success
ladle	✅ success
laravel	✅ success
marko	✅ success
nuxt	✅ success
previewjs	✅ success
qwik	✅ success
rakkas	✅ success
sveltekit	✅ success
vite-plugin-ssr	✅ success
vite-plugin-react	✅ success
vite-plugin-react-pages	✅ success
vite-plugin-react-swc	✅ success
vite-plugin-svelte	✅ success
vite-plugin-vue	✅ success
vite-setup-catalogue	✅ success
vitepress	✅ success
vitest	✅ success
windicss	✅ success

[bluwy]

I wonder if we should try to fix this first since the bug has not been released yet. Using the test from #12528,

export * from './module-a.js'
export { getValueAB } from './module-b.js'

Reverting this fixes it since we provide an export value from './module-a.js' before './module-b.js' access it. It also runs well in Node. However this seems to be unique to export * only. If I change this to:

export const valueA = 'circ-dep-init-a'
export { getValueAB } from './module-b.js'

It errors in Node. Testing things around, e.g. with:

 const foo = 'bar'
 export {foo}

 export * from './module-a.js'

console.log(getValueAB())
import { getValueAB } from './module-b.js' // <-- also tries to read `foo`, but fails

I think the rule is that:

1. re-exports gets hoisted to the highest level
2. then hoist import statements

Right now this order is not guaranteed, I'm testing a fix locally for now.

[patak-dev]

Closing as #12530 has been merged