Fix: add missing await when creating Abstract client

[LisaMoore01]

Ensure that the result of createAbstractClient is awaited within queryFn so that the resolved client instance is returned.

This improves consistency and avoids potential issues with unresolved promises.

---

PR-Codex overview

This PR focuses on changing the instantiation of the client in the useAbstractClient.ts file to use await, indicating that createAbstractClient is now an asynchronous operation.

Detailed summary

• Changed const client = createAbstractClient({ to const client = await createAbstractClient({ to handle the asynchronous nature of createAbstractClient.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8328398

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

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

Click here to learn what changesets are, and how to add one.

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

[cursor]

PR Summary

Low Risk
Low risk one-line change that ensures the React Query queryFn returns a resolved client instance instead of a pending Promise.

Overview
Fixes useAbstractClient to await createAbstractClient(...) inside the React Query queryFn, ensuring the query resolves to an initialized Abstract client rather than returning an unresolved promise.

^{Written by Cursor Bugbot for commit 8328398. This will update automatically on new commits. Configure here.}