useLazyLoadQuery execution on Next 13 and React 18

I'm seeing a somewhat surprising behaviour of `useLazyLoadQuery` on Next 13 and React 18. It seems that `useLazyLoadQuery` fetches the data within render, instead of being a noop on the server.

This is a bit surprising. How would achieve it being a noop on the server (and/or make it suspend), and only fetch it on client?

Another tricky thing with this new behaviour is that the `initialRecords` are usually gathered in the `getServerSideProps` method, and the queries that run within render are executed after, and thus won't be sent to the client to be hydrated. This means that another query will be issues client side, which will lead to server/client missmatches.

No files or tests are named. Reproduce useLazyLoadQuery with Next 13, React 18, getServerSideProps, and initialRecords, then trace server rendering and client hydration to establish the intended behavior. Done requires an agreed server no-op or suspension model that avoids duplicate client fetches and server/client mismatches.

Written by the indexing model from the issue text.