V9 (vue) reduce unref overhead by supporting getter functions for configuration

[teleskop150750]

Description

Is your feature request related to a problem?

Yes. Currently, the Vue adapters in the TanStack ecosystem (such as @tanstack/table-vue and @tanstack/vue-query) lean heavily into deep object resolving using unref or custom deeply-unwrapping helpers (often referred to as the maybeRef anti-pattern in the Vue community).

While this mimics React's flat dependency/configuration model, it introduces significant runtime overhead in Vue. The library spends extra CPU cycles deeply traversing configuration objects and data structures to unwrap potential refs at every lifecycle step, even when the user passes static data or handles reactivity themselves.

Describe the solution you'd like

Instead of forcing the internal codebase to deeply inspect and unwrap every single configuration property, the library could adopt a design similar to @tanstack/solid.

We should allow users to pass a getter function that returns a clean, plain JavaScript object. This shifts the responsibility of reactivity resolution to Vue's native reactivity tracking mechanism (like computed or standard getter evaluation) and leaves the choice of how to unwrap refs to the user.

Implementation Example

Pinia colada

useQuery({
-   key: ['todos', { page: computed(() => route.query.id) }],
+  key: () => ['todos', { page: route.query.page }], 
  // ...
})