fix: Ensuring that useQuery's isFetching becomes true after query changes

[Chriztiaan]

An issue was found where if the query or parameters change for useQuery, there would be single render cycle where isFetching was false before it became true.

For example:

1. isFetching: false // query changed but the variable is still false
2. isFetching: true // state has been updated
3. isFetching: false // query has finished re-executing

This fix ensures that isFetching is correctly set to true as soon as the hook executes due to a query change.

1. isFetching: true // query change causes hook to execute, compare current query to new query - 
track with internal `shouldFetch` variable.
2. isFetching: true // state has been updated
3. isFetching: false // query has finished re-executing

[changeset-bot]

🦋 Changeset detected

Latest commit: 4d7b42f

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

This PR includes changesets to release 3 packages

Name	Type
@powersync/react	Patch
@powersync/react-native	Patch
@powersync/diagnostics-app	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

[fooware]

In our case, we had multiple renders with isFetching being incorrectly false in combination with the old stale data, probably due to us having multiple useQuery hooks firing and re-rendering things.

I have tested @Chriztiaan's changes locally, and the latest version in this PR resolves the issue for us.