When we have a specified graphql endpoint, and that endpoint doesn't match we don't need to parse
the request at all.  This avoids weird console.errors that may apply when the user mixes rest and d
graphql handlers. This fix cannot be easily applied to the base `graphql` handler since it doesn't
have a dedicated endpoint, but that's a decent tradeoff for now, as it provides a way to better
scope those errors and avoid user confusion in the short term.

Maybe we should consider forcing graphql calls to `link` a specific endpoint prior to handling which
would avoid this issue