fix: remove return type of promise from refresh and execute.

[tdekoning]

🔗 Linked issue

#25558

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 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)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

The TypeScript definition didn't match the implementation. The promise chain of useAsyncData does not return a value, but updates the returned Ref values.

This solves the problem that developers expect these functions to return data.

Resolves #25558

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[danielroe]

We could also consider returning the data.

[manniL]

@danielroe Do you think that'd be beneficial or rather result in misuse of e.g. useFetch? 🤔

[danielroe]

The name definitely suggests not returning the data so I think probably better to merge as is.

[manniL]

@tdekoning could you also update the types in the docs?

[tdekoning]

@manniL you mean here ? They already seem to be properly typed.

[manniL]

Ah, perfect! Already strange that they were out of sync then! Thanks for checking 👍