feat!: make import.meta.hot.send async

[sapphi-red]

Description

The error that happened inside send method of ModuleRunnerTransport was not able to handle.

This PR fixes that by awaiting on the send method. This requires the import.meta.hot.send to be also awaited (thus a breaking change). This await was not required in Vite 5 because we only used WS and WS's send is sync. In #18362, I made the ModuleRunnerTransport to allow async send just because I thought there may be a place that require async and didn't find any breaking change by doing so.

Alternative way to solve this is #18751.

[sapphi-red]

/ecosystem-ci run

[vite-ecosystem-ci]

📝 Ran ecosystem CI on 2b692b7: Open

suite	result	latest scheduled
astro	❌ failure	❌ failure
histoire	❌ failure	❌ failure
redwoodjs	❌ failure	❌ failure
remix	❌ failure	❌ failure
sveltekit	❌ failure	❌ failure
vike	❌ failure	❌ failure
vitest	❌ failure	✅ success
waku	❌ failure	❌ failure

✅ analogjs, ladle, laravel, marko, nuxt, previewjs, quasar, qwik, rakkas, storybook, unocss, vite-environment-examples, vite-plugin-pwa, vite-plugin-react, vite-plugin-react-swc, vite-plugin-svelte, vite-plugin-vue, vite-setup-catalogue, vitepress, vuepress

[sapphi-red]

closing as #18753 was merged