fix(client-nuxt): forward asyncDataOptions to useFetch and useLazyFetch
asyncDataOptions (e.g. { immediate: false }) was destructured out of
request options but only forwarded to useAsyncData/useLazyAsyncData.
The useFetch/useLazyFetch path silently ignored it, causing fetches
to fire immediately regardless of the immediate option.
Nuxt's useFetch accepts these options as top-level keys, so spreading
asyncDataOptions into the options object is the correct fix.
Closes #1966
Closes #1785