Added new option for bypassing requests with GET query parameters

@kwhitley,

I found myself using this bypass in an edge case where a route is largely controlled by query parameters. For instance, I have a route that processes up to 10 different filters (including: limit, offset, state, search, option1, option2, etc.). However, since each user for this route will have unique specific needs, it makes little sense to cache requests with these specific query parameters. However, having the default route cached can make a significant difference.

So, I implemented a `bypassQuery` option for these needs. Let me know what you think!