Replace the deprecated cache with query (#1075)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

Author: amirhhashemi

src/routes/guides/routing-and-navigation.mdx

@@ -493,7 +493,7 @@ This means you can initialize the page, or use [Data APIs](/solid-router/referen
 
 <Callout>
 	To prevent a fetch from happening more than once, or to trigger a refetch, you
-	can use the [`cache` function](/solid-router/reference/data-apis/cache).
+	can use the [`query` function](/solid-router/reference/data-apis/query).
 </Callout>
 
 ```jsx title="index.jsx"

src/routes/solid-router/reference/data-apis/create-async.mdx

@@ -7,7 +7,7 @@ An asynchronous primitive with a function that tracks similar to `createMemo`.
 Reading it before it is ready causes Suspense/Transitions to trigger.
 
 <Callout type="caution">
-	Using `cache` in `createResource` directly will not work since the fetcher is
+	Using `query` in `createResource` directly will not work since the fetcher is
 	not reactive. This means that it will not invalidate properly.
 </Callout>
 

src/routes/solid-router/reference/data-apis/query.mdx

@@ -85,7 +85,7 @@ For instance, both `{ name: 'Ryan', awesome: true }` and `{ awesome: true, name:
 
 ## Return value
 
-The return value is a `CachedFunction`, a function that has the same signature as the function you passed to `cache`.
+The return value is a `CachedFunction`, a function that has the same signature as the function you passed to `query`.
 This cached function stores the return value using the cache key.
 Under most circumstances, this temporarily prevents the passed function from running with the same arguments, even if the created function is called repeatedly.
 

src/routes/solid-start/advanced/return-responses.mdx

@@ -3,7 +3,7 @@ title: Returning responses
 ---
 
 In SolidStart, it is possible to return a Response object from a server function. 
-[`solid-router`](/solid-router) knows how to handle certain responses with its [`cache`](/solid-router/reference/data-apis/cache) and [`action`](/solid-router/reference/data-apis/action) APIs. 
+[`solid-router`](/solid-router) knows how to handle certain responses with its [`query`](/solid-router/reference/data-apis/query) and [`action`](/solid-router/reference/data-apis/action) APIs. 
 For Typescript, when returning a response using `solid-router`'s `redirect`, `reload`, or `json` helpers, they will not impact the return value of the server function.
 
 While we suggest depending on the type of the function to handle errors differently, you can always return or throw a response.

src/routes/solid-start/advanced/session.mdx

@@ -41,7 +41,7 @@ export async function getUser(): Promise<User | null> {
 
 This helper can be used wherever you want to authenticate the request, including in server functions and [API routes](/solid-start/building-your-application/api-routes).
 
-Additionally, you can use it with [`cache`](/solid-router/reference/data-apis/cache) from `solid-router` to make sure that only authenticated users can access the data.
+Additionally, you can use it with [`query`](/solid-router/reference/data-apis/query) from `solid-router` to make sure that only authenticated users can access the data.
 That way if the user is not authenticated, the request will be redirected to the login page.
 
 ```tsx title="/routes/api/store/admin.ts"