fix: keep sponsor data composables in Nuxt context

Nuxt documents useFetch as a composable that should be called directly in setup, plugins, or route middleware so it can register payload state for hydration. Calling useFetch and useAsyncData directly in this composable keeps the Nuxt data primitives visible instead of hiding them behind a generic Promise.all boundary.

The call sites can still include useSponsors() in their existing Promise.all arrays; Promise.all accepts plain values, and the composable keeps returning the same sponsors helpers.

Docs: https://nuxt.com/docs/4.x/api/composables/use-fetch

Author: onmax

app/composables/useSponsors.ts

@@ -1,10 +1,8 @@
 import type { Sponsor } from '#shared/types'
 
-export const useSponsors = async () => {
-  const [{ data: apiSponsors }, { data: manualSponsors }] = await Promise.all([
-    useFetch('/api/sponsors', { key: 'sponsors' }),
-    useAsyncData('manual-sponsors', () => queryCollection('manualSponsors').first())
-  ])
+export const useSponsors = () => {
+  const { data: apiSponsors } = useFetch('/api/sponsors', { key: 'sponsors' })
+  const { data: manualSponsors } = useAsyncData('manual-sponsors', () => queryCollection('manualSponsors').first())
 
   const sponsors = computed(() => {
     const manual = manualSponsors.value?.sponsors || []