fix: disconnect from Kafka on process exit

[kalinkrustev]

When deployments in k8s are restarted or scaled down, the pods that get terminated must make sure that all created consumers are explicitly disconnected. If consumers are not disconnected, Kafka still sees the old connections and there is and increased delay for rebalancing the corresponding consumer group.

The process exit event does not allow async processing, that's why this helper module is used.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[kalinkrustev]

I checked other places where signals events are attached, all I saw call process.exit() at most 10 seconds after the signal. This also the default of async-exit-hook, so it should work fine.