Deploying with a custom authorizer automatically sets authorization caching

For the time being I have authorization caching disabled in my API Gateway but whenever I redeploy my chalice package it activates caching. I can look into what it would take to accept an optional caching param and submit a PR if that seems like a good idea? I would see it working as caching being on by default as is, but if i specified `caching=False` it would make sure that box was unchecked.

Start by tracing Chalice package deployment for a custom authorizer and where authorization caching is configured. Done means an optional caching=False setting keeps caching disabled while the existing default remains enabled.

Written by the indexing model from the issue text.