fix: ensure correct order of template effect values (#16655)

Compiler does sync then async but `memoizer.apply` did it the other way around

Author: dummdidumm

.changeset/healthy-crabs-marry.md

@@ -0,0 +1,5 @@
+---
+'svelte': patch
+---
+
+fix: ensure correct order of template effect values

packages/svelte/src/compiler/phases/3-transform/client/visitors/shared/utils.js

@@ -34,7 +34,7 @@ export class Memoizer {
 	}
 
 	apply() {
-		return [...this.#async, ...this.#sync].map((memo, i) => {
+		return [...this.#sync, ...this.#async].map((memo, i) => {
 			memo.id.name = `$${i}`;
 			return memo.id;
 		});

packages/svelte/tests/runtime-runes/samples/async-template-async-sync-mixed/_config.js

@@ -0,0 +1,9 @@
+import { tick } from 'svelte';
+import { ok, test } from '../../test';
+
+export default test({
+	async test({ assert, target }) {
+		await tick();
+		assert.htmlEqual(target.innerHTML, '<p>foo bar</p>');
+	}
+});

packages/svelte/tests/runtime-runes/samples/async-template-async-sync-mixed/main.svelte

@@ -0,0 +1,17 @@
+<script>
+	function foo() {
+		return 'foo';
+	}
+
+	async function bar() {
+		return Promise.resolve('bar');
+	}
+</script>
+
+<svelte:boundary>
+	<p>{foo()} {await bar()}</p>
+
+	{#snippet pending()}
+		<p>pending</p>
+	{/snippet}
+</svelte:boundary>