[Idea] Automatically enable load from cache in explorer if query contains client-only fields


The experience of running queries with client-only fields in embedded explorer has some room for improvement:
- field triggers a red squiggle because we're dealing with the introspected schema
- client-only fields can only be fetched from the cache, so by default they won't appear in the response unless you see and then tick the 'load from cache' checkbox

An easy win might just be automatically enabling 'load from cache' for queries with these fields, but there's a tradeoff with potentially stale data being returned for other fields which may not be acceptable if the user is expecting it to hit the network.

Happy to eventually move this issue elsewhere but tracking it here for now.

Start by locating the embedded explorer's handling of client-only fields and the “load from cache” checkbox. Reproduce a query containing a client-only field and examine how cache loading currently affects the response. Done requires an agreed behavior for stale network fields as well as coverage for the selected behavior.

Written by the indexing model from the issue text.