Pipelinewise-tap-kafka

------------------
**BREAKING CHANGES**

Upgrading from 6.x to 7.x: For the current taps without any primary keys defined, set new configuration property `use_message_key` to `false`. Taps left with default settings and no custom primary keys specified will fail if kafka messages do not have keys and lead to unexpected behaviour on targets otherwise.

*Features*:
- Added support for the message keys to be used as primary key for the record. Using message key is now a default option where custom PKs are not defined.

------------------

- Use unique proto class names per topic
- Raise exception on all brokers down
- Raise exception if custom PK not exists in the message
- Bump `dpath` from `2.0.5` to `2.0.6`
- Bump `grpcio-tools` from `1.43.0` to `1.44.0`
- Bump `pytest` from `6.2.5` to `7.0.1`

------------------
*Features*:
- Add protobuf support

*Fixes*:
- Fixed an issue when log messages raised exceptions

*Requirement updates*:
- Bump `dpath` from `2.0.1` to `2.0.5`
- Bump `pytest-cov` from `2.10.1` to `3.0.0`
- Bump `pylint` from `2.4.2` to `2.12.2`
- Remove `filelock` requirement

------------------

- Fixed an issue when `tap_kafka.serialization` module not included in the package

------------------
**BREAKING CHANGES**

Upgrading from 4.x to 5.x: Please remove the existing `state.json` created by tap-kafka 4.x.
5.x will continue consuming messages from the last consumed offset but will generate `state.json` in a new format.

**CHANGELOG**
- Switching from `kafka-python` to `confluent-kafka-python`
- Using faster `orjson` provided by `pipelinewise-singer-python-2.x`
- Remove local store and bookmark consumed message in `STATE` messages
- Add `initial_start_time` optional parameter

------------------
*Fixes*:
* Fallback to default consumer timeout if `consumer_timeout_ms` is not provided in discovery mode.
* Stop mis-handling exceptions during discovery.