Refactor bootstrapping logic out of ClusterContext

Currently, the bootstrapping logic for a bucket is split between the ClusterController and the Bucket implementation itself. This makes it impossible to defer all bootstrapping errors to the CouchbaseCollection level as a thrown exception will put the Bucket in a inconsistent state. This ticket is to consolidate the bootstrapping logic to the bucket level and properly defer any exceptions until a KV or other collection level method is called.