RePause All Partitions After Rebalance if user paused any and requested

[Gin2022Null]

Resolves #307

In order to achieve graceful shutdown during deployment, We applied the following strategy:

1. Pause old kafka consumer
2. Process in-flight messages
3. Application fully shutdown.
   But when new consumers join the consumer group, after rebalance, old consumers wake up, if the newly assigned partitions are not in the pausedByUser, consumer start poll messages which gracefully shutdown are not fully achieved.

Add pauseAllAfterRebalance configuration
When a user pauses topics/partitions before rebalancing, the behavior depends on the value of pauseAllAfterRebalance.If it is set to False, the paused topics/partitions will remain paused after the rebalance. However, if it is set to True, all assigned topics/partitions will be paused after the rebalance.

Test:
ReceiverOptions.create(props).pauseAllAfterRebalance(Boolean.TRUE);

Consumer-1 assigned partitions: testTopic-2
Consumer-2 assigned partitions: testTopic-0, testTopic3-1

Consumer-2 Pause Topic/Partitions
Kafka Consumer Template status=PAUSE topic=testTopic, partition=0
Kafka Consumer Template status=PAUSE topic=testTopic, partition=1

Consumer-3 join - rebalance
Consumer-2 Revoke previously assigned partitions testTopic-0, testTopic-1
Assignment(partitions=[testTopic-2])}

testTopic-2 paused.

[pivotal-cla]

@Gin2022Null Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

[pivotal-cla]

@Gin2022Null Thank you for signing the Contributor License Agreement!

[garyrussell]

Thanks for the contribution; LGTM, except we should use boolean instead of Boolean.