feat(devservices): Add containerized taskbroker to devservices config

[hubertdeng123]

With the revamped devservices, the configurations for how to run taskbroker should live in this repo and not sentry.

See snuba: https://github.com/getsentry/sentry/blob/ec05e95588181966ded878090b1241e3b3fb2775/devservices/config.yml#L6

This allows configurations to be defined in the appropriate repo and be used anywhere else.

[evanh]

How does this address get set correctly? I notice it's different from the one defined in snuba, and different from the name of the current kafka devservice (which is called sentry_kafka).

[markstory]

Yes, the new devservices command uses different host names. I've also noticed that the devservices container has 9092 exposed instead of 9093.

[hubertdeng123]

I think this should actually be fine, we're using mostly the same settings as before and taskbroker should be communicating on the docker internal network which should use port 9093 as defined here: https://github.com/getsentry/sentry-shared-kafka/blob/c8ab4ee7627d435c4c5ebccf21c5744950eac1f6/devservices/config.yml#L25.

If taskbroker cannot properly connect to kafka, will it error out anywhere? How can we tell it is properly configured?

[markstory]

Yes, taskbroker will error and crash if it cannot connect to Kafka.