fix(kafka): Handle message indices in proto data also for Glue Schema Registry

[phipag]

Issue #, if available: N/A

Description of changes:

Copy of #1906

Thanks to @karthikpswamy for contributing this logic!

Description of changes:

* Adding support for different schema registry types (Confluent and Glue)

* Improving the handling of message indices in protobuf data

* Fixing deserialization logic for different schema registry formats

* Adding appropriate tests for both Confluent and Glue schema registry scenarios

Schema Registry Type Detection and Deserialization Logic:

No Schema Registry Integration:

* When KafkaEvent contains no key/value metadata

* Uses entire byte array as raw data for deserialization

* AWS Glue Schema Registry:

Identified by 16-byte schema ID in key/value metadata

* Skips first byte of data

* Uses remaining bytes for Protobuf deserialization

* Confluent Schema Registry:

Default case when neither of above conditions are met

* Follows Confluent wire format specification

* Dynamically skips 1 or 2 bytes based on message index

* Uses remaining bytes for Protobuf deserialization

Checklist

• Meet tenets criteria
• Update tests
• Update docs
• PR title follows conventional commit semantics

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud