fix(nuxt3): improve error types for useAsyncData and useFetch

[Mini-ghost]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Let useFetch() and useLazyFetch() return error can defined type by generics, like below:

const { data, error } = useFetch<TData, TError>('url')

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[netlify]

✅ Deploy Preview for nuxt3-docs ready!

Name	Link
🔨 Latest commit	20d9556
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/626c30bd4ff998000828e02e
😎 Deploy Preview	https://deploy-preview-4210--nuxt3-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[Mini-ghost]

@danielroe I adjusted the generics naming, but I'm not sure why the test the CI / test-fixtures (windows-latest, 16) is wrong

[pi0]

@danielroe Can you please check this PR for refactors?

[pi0]

Thanks @Mini-ghost @danielroe 💚