Skip using the GraphQL cache if a token is passed

[DanielDarrenJones]

If a token is passed in the request we want to avoid using the cache so that our live preview can display the changed results, we need to perform this logic both in the get method to actually ensure we skip the cache when getting the value, but also in the put so that we don't override the standard cache with our temporary values.

Fixes #5389

[jasonvarga]

Thanks but this isn't quite enough. It needs to be a valid token, otherwise anyone could slap ?token=whatever onto the graphql route and bypass the cache. It also needs to support being able to pass the token through a header.

I'll address it in a separate PR. Thanks!