Cluster settings like compression, tracing, etc.. should be set at Cluster initialisation only

In PYCBC-775, we added a bunch of settings to cluster which propagate down to all the buckets as well. Lets make sure when we create new buckets after a call to one or more of the setters for the various options, that bucket gets these settings as well.

Ideally we will wait on this until we do 2 things:
(1) share connections across collections that share the same bucket (PYCBC-815)
(2) rework the test framework to not use the ClassicAuthenticator as this makes that cluster's subsequent open_bucket calls always fail (PYCBC-832)

Of course, having an object that held all these settings (like an environment of some sort) is ideal. But maybe we can just cache the settings that changed in cluster, and use that to call the settings on the new bucket, etc...