feat: expose loading and error fields of async computed signal

[Varixo]

Expose (hidden until now) loading and error fields of async computed signal

[changeset-bot]

🦋 Changeset detected

Latest commit: 0dbff0a

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/QwikDev/qwik/@qwik.dev/core@7876

npm i https://pkg.pr.new/QwikDev/qwik/@qwik.dev/router@7876

npm i https://pkg.pr.new/QwikDev/qwik/eslint-plugin-qwik@7876

npm i https://pkg.pr.new/QwikDev/qwik/create-qwik@7876

commit: 0dbff0a

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
qwik-docs	✅ Ready (View Log)	Visit Preview	0dbff0a

[wmertens]

I wonder if we really need an error field, let alone a signal for it? Shouldn't errors be never happening?

[Varixo]

I wonder if we really need an error field, let alone a signal for it? Shouldn't errors be never happening?

if you call fetch inside async computed and fetch fails, then I think we should handle this somehow

[wmertens]