Block create_bucket with timeSync parameter on mixed mode cluster 410 and 450

This likely ties in with https://issues.couchbase.com/browse/MB-20005

1. During online upgrade, 1 node is in 410 and other node is in 450
2. Create a bucket with timeSync enabled - the create_bucket call is successful, though it ignores the timeSync parameter.

The expectation is that the creation of the bucket itself should be blocked for 410-450 mixed clusters.

https://s3.amazonaws.com/cb-engineering/2/collectinfo-2016-06-22T153924-ns_1%4010.1.5.23.zip
https://s3.amazonaws.com/cb-engineering/2/collectinfo-2016-06-22T153924-ns_1%4010.1.5.25.zip