[MB-39088] - DCP client name doesn't consider bucket dataverse

Affects version: 6.5.x

When a KV bucket is referenced from two different dataverses, the generated CBAS DCP client name doesn't consider the bucket dataverse. This will cause two different DCP clients to share the same name and the DCP producer will end up closing one of them.

Following is the error message that is observed in memcached logs:

Disconnecting existing Dcp Producer<> as it has the same name as a new connection <>

Solution is to upgrade to 6.6.0 or workaround is to ensure that all datasets that reference the same bucket are kept in the same dataverse which will prevent the Analytics Services creating connections with the same name.