KAFKA-19511: Fix flaky test HandlingSourceTopicDeletionIntegrationTest.shouldThrowErrorAfterSourceTopicDeleted

[RaidenE1]

Ticket here: https://issues.apache.org/jira/browse/KAFKA-19511

Original timeout for HandlingSourceTopicDeletionIntegrationTest is 60s
which is not enough. Sometimes the state of Kafka streams thread needs
around 100s to change the state from PENDING ERROR to ERROR, as it still
try to poll data while the source topic is missing, also while leaving
the consumer group it will reach the timeout for 30s.

[mjsax]

Thanks for the PR. I am not sure if I fully understand. I believe this issue with this test was introduced when streams protocol was added. But why does it modify the behavior in the way you describe?

What you describe sounds very generic and I am wondering why it was not a problem for classic protocol?

Btw: Looking into the test, it seems we are leaking KafkaStreams() instances, as we don't close() them. Can we extend this PR to use try-with-resource to ensure we don't leak instances?

Another minor fix could be, to replace Serdes.Integer().getClass() in the config setup with Serdes.IntegerSerde.class.

[RaidenE1]

@mjsax Yeah, it only happens in the new protocol, I've run it for a hundred times maybe, old protocols are all good, half of the new test spend 100s and failed the original test since it's set to 60s.