Change DCP name to avoid Data Service issues

There is a known issue within KV engine (tracked as MB-48655) where DCP clients with

{ or } in the name are not logged properly from within memcached. This makes diagnosing DCP issues with the connector difficult, as there is little logging to go on.

The aforementioned issue is fixed in 7.1 likely through an update of the logging component used, however with the release cadence of server vs clients, it might make sense to make some adjustments here to mitigate the issue sooner (and avoid people having to do a 7.1 upgrade straight away).

The suggestion here is to ensure the DCP name registered doesn't contain { or }

and probably also take into account MB-34280 where names > 200 characters cause things to break.