perf(vue): use shallowRef for data

[yurks]

Summary

As graphql response usually contains a quite huge nested objects structure, wrapping it with ref() is not memory efficient.
Instead of doing this, it's more efficient to use shallowRef() for data reactive variable, where the payload is stored.

However, in #3611 while optimizing other variables, @negezor missed the data variable. I can assume there was a reason for that, so I consider this PR as a suggestion/discussion. Personally, I don't see any negative side effects from using shallowRef(), but maybe you guys have some thought on it.

I see only one possible scenario in which this would be a "breaking change": updating some nested data parts manually outside of this plugin, but I'd say - this is a quite specific pattern.

Set of changes

• Replaces ref() with shallowRef() for the data variable

[changeset-bot]

🦋 Changeset detected

Latest commit: fc215b0

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

This PR includes changesets to release 1 package

Name	Type
@urql/vue	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

[negezor]

Makes sense, I wasn't originally looking at data as to how field level changes might be happening there. But I forgot that we always replace the contents of ref 😅

[kitten]

Don't really see what could go wrong here, since types aren't relevant and computed was already mentioned and recommended across several issues/discussions 👍