Dropping Authorization from graphql hash

[pdohogne-magento]

This code is in the framework code for the hash subroutine:

  if( req.url ) {
    set req.hash += req.url;
    set req.hash += req.http.Host;
    set req.hash += req.http.Authorization;
    set req.hash += req.http.Fastly-SSL;
    set req.hash += req.vcl.generation;
    return (hash);
  }

However, req.http.Authorization being included in the hash means that every single user will get a different request id, which is not desired; the cache should be shared between users.

To fix this, this PR takes that same block but omits the Authorization header and returns before the Fastly-side code runs.

[pdohogne-magento]

@vvuksan Please take a look at this PR and offer your thoughts. We've also pinged you in the Magento Community slack.

[vvuksan]

This workaround addresses a deficiency that was introduced in a vendor's tooling that added Authorization header to the cache key resulting in GraphQL queries not to cache efficiently. This change forces the cache key only for GraphQL paths.