Refactor bootstrapping so client doesn't try CCCP by default for memcached buckets

1) Currently, the client will try to bootstrap with CCCP by default and then fail if it's a Memcached bucket and then HTTP streaming will tried. This should add functionality for either determining the bucket type upfront from Admin API or using input from the config (IsMemcached=true) so that the CCCP try can be skipped.

2) Add support for "fail fasting" bad configs (for instance a bucket doesn't exist) in certain scenarios instead of try to connect over and over again.

*Note these could be sub tasked with this ticket as the parent or bifurcated into two separate tasks.