fix(openapi-react-query): propagate undefined errors from empty-body non-OK responses

[EduardF1]

Closes #2070.

What changed and why

• update queryFn, useInfiniteQuery's queryFn, and mutationFn to throw when error !== undefined || !response.ok
• destructure response anywhere it was missing so the non-OK HTTP status is available
• add regression tests covering empty-body non-OK responses for query, mutation, and infinite query paths

Scenario fixed

When openapi-fetch returns { data: undefined, error: undefined, response } for a non-OK response with an empty body (for example, a 4xx/5xx response with Content-Length: 0), the previous if (error) check treated the result as successful and swallowed the failure. This change propagates those undefined errors correctly by also checking response.ok.

[netlify]

👷 Deploy request for openapi-ts pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	bdf4abf

[changeset-bot]

🦋 Changeset detected

Latest commit: bdf4abf

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

This PR includes changesets to release 1 package

Name	Type
openapi-react-query	Patch

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

[EduardF1]

Thanks for the changeset reminder. This change should ship as a patch for openapi-react-query, so I will add a changeset for that package to keep the release metadata accurate.

[EduardF1]

Added the missing changeset for \openapi-react-query\ and pushed it in bdf4abf.