Handle poison pills in message Confluent Schema Registry Avro decoder

Currently, when bad messages are ingested by Pinot these messages fail decoding and stop consumption of the stream sending the segments to `OFFLINE` state. There is no easy way to recover from this state.

Most of these issues are caused during deserialisation of the binary data into the ingestion format. Some. examples of bad messages included Avro messages with magic byte missing, JSON messages with invalid format, incompatible CSV messages.

The behaviour of the decoder could be governed by config properties of for any reason the current behaviour needs to be kept as is.

Start by locating Pinot's Confluent Schema Registry Avro decoder and the ingestion deserialization path it uses. Determine how poison messages currently stop stream consumption, then define configurable behavior for handling decode failures while preserving the existing behavior when requested; done means bad messages no longer force segments offline under the new setting.

Written by the indexing model from the issue text.