fix: use-resource not catching onRejected

[maiieul]

What is it?

• Bug

Description

It used to be like that and got removed by inadvertance in e33abbb I think. This causes some cypress component tests to fail because of unhandled rejection errors.

Checklist

• My code follows the developer guidelines of this project
• I performed a self-review of my own code
• I added a changeset with pnpm change
• I made corresponding changes to the Qwik docs
• I added new tests to cover the fix / functionality

[changeset-bot]

🦋 Changeset detected

Latest commit: 7d62aa2

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

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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/@builder.io/qwik@8197

npm i https://pkg.pr.new/@builder.io/qwik-city@8197

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

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

commit: 0142532

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
qwik-docs	✅ Ready (View Log)	Visit Preview	7d62aa2

[JerryWu1234]

logic looks solid. By attaching a dummy catch. we prevent the runtime from flagging the promise as "unhandled" before our custom onRejected handler has a chance to process the state.
Nit: Please add a comment like // Suppress unhandled rejection warning above the line so future contributors don't remove it thinking it's mistake

[wmertens]