Add support for using different subject name strategies

[enamrik]

Description

This is my attempt at adding support for subject name strategies. All new behavior is triggered by new configuration parameters to avoid breaking changes.

Changelog:

• By default, xk6-kafka's schema registry based serializers only support the TopicName subject name strategy. To enabled the other two subject name strategies (RecordNameStrategy and TopicRecordNameStrategy) on a producer, set the subjectNameStrategy property on the producer configuration to the name of the desired strategy. To enable on a consumer, set the subjectNameStrategy property on the consumer configuration to the name of the desired strategy

const configuration = JSON.stringify({
    consumer: {
        keyDeserializer: "",
        valueDeserializer: "io.confluent.kafka.serializers.KafkaAvroDeserializer",
        useMagicPrefix: true,
       subjectNameStrategy: "RecordNameStrategy",
    },
    producer: {
        keySerializer: "",
        valueSerializer: "io.confluent.kafka.serializers.KafkaAvroSerializer",
        subjectNameStrategy: "RecordNameStrategy",
    },
    schemaRegistry: {
        url: "http://schema-registry:8081",
    },
})

• Once a message has been published with the schemaID magic prefix, when consuming, the magic prefix can be extracted and used to get the schema. This allows dynamic schema resolution for the consumer without needing to specify the consumed message's schema. To enable this functionality, add useMagicPrefix: true to the consumer configuration.

[mostafa]

Thanks for your contribution! 🙏
I left a few comments.

For reference:

• Choosing Schema Registry Subject Name Strategy #85

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
4 Code Smells

No Coverage information
0.0% Duplication

[mostafa]

LGTM! 🙏