Fix proto parsing for unparseable Kafka message

[saithal-confluent]

Description

Fixed the bug which causes ingestion halt for invalid proto message

When Druid encounters an invalid protobuf kafka message, the ingestion on that partition gets halted as hasNext() method of the FilteringCloseableInputRowIterator.java gets stuck in a endless while loop, until maxParseExceptions is reached.
The fix is to seek the byte buffer to its limit whenever there's a parsing failure. This would allow the buffer to move on and not get stuck at the same place.

Release note

For tips about how to write a good release note, see Release notes.

---

Key changed/added classes in this PR

• MyFoo
• OurBar
• TheirBaz

---

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[pagrawal10]

LGTM