KAFKA-20072 Make Uuid no-dash behavior opt-in

[mumrah]

Instead of changing Uuid#randomUuid to always have the new behavior
introduced in #21313, this patch moves the new logic into a separate
randomUuidNoDashes method.

Since Uuid is a utility class, it is used widely throughout the broker
and client (possibly even applications). In most cases, the presence of
a dash is inconsequential. The new behavior, which comes with a small
performance hit, should not affect these callers. The introduction of a
new Uuid factory makes the new behavior opt-in.

One caller is updated to use the new factory which is where the
controller allocates topic IDs. This matches the intention of the
original Jira.

[mumrah]

cc @mimaison @ijuma

[nileshkumar3]

Nice, clear change making the no-dash behavior opt-in via randomUuidNoDashes() and using it in ReplicationControlManager#createTopic — that matches the intent of KAFKA-20072 for topic IDs. Should bin/kafka-storage.sh random-uuid, or any other operator-facing ID generation sites, remain unchanged, or would it make sense to consider them as a follow-up?