Mirror should consume from non Quick topics

[raminqaf]

Imagine the following scenario, if a user has a topic filled with records and only wants to query them, they only need a mirror that consumes the data from their topic. But now they have to create a topic with quick move their records to the new topic to make them queryable. This limits the users.

We should consi der updating the mirror creation command in the CLI so it sends the correct key and value type. The manager should check the Internal Topic Registry and register the topic with the correct key and value type. This check can be done in the KubernetesMirrorService.