As a Swatch developer, I want to enable Swatch to consume from the new Kafka topic in parallel with the existing UMB topic (VirtualTopic.services.productservice.Product).   I want the new Product kafka consumer to invoke the same downstream codepath as the legacy consumer so that product updates behave consistently, regardless of which consumer processes a SKU first.

This is almost identical to what we did in SWATCH-3456, except we're doing kafka now instead of UMB.

Note:  Integration Testing in stage is dependent on getting the name of the new kafka topic, and making sure our certs are ok to authenticate on it (could be a different card?)

Entrance Criteria:

• Have they finalized what the schema of the new kafka messages are going to be?  Are they the same as the umb message?

Acceptance Criteria:

• swatch subscribes to the new kafka topic alongside the legacy umb topic
• logging should distinguish which topic a message is being consumed from
• messages from the new topic use the same logic as messages consumed from the legacy topic
• validate that both consumers result in consistent product metadata
• testing should include test cases that:
  • new consumer receives a SKU before the legacy one
  • legacy consumer receiving a SKU before the new one
  • both consumers receive the same SKU in close succession