Expose schema metadata in AvroDeserializer (Issue #2046)Fix/avro deserializer schema info

[harrold-mussa]

What

This is about Issue #2046 and I'm trying to allow the AvroDeserializer to optionally return message metadata (specifically the Schema ID and the Writer Schema) alongside the deserialized record.

This info is calculated during __deserialize but is not accessible to end-user.

Checklist

• Contains customer facing changes? Including API/behavior changes
• Did you add sufficient unit test and/or integration test coverage for this PR?
• I have verified the logic with a local mock script and am looking for guidance on where to best place the permanent unit tests within the codebase.

References

GitHub Issue: #2046

Test & Review

• I used a custom verification script to mock the SchemaRegistryClient and the schemaless_reader.
• I verified that without the flag, the behavior remains identical to the current master branch.

Open questions / Follow-ups

• I need help identifying a file to define the init for the toggle. The inheritance structure is quite difficult for me, and I want to ensure I'm adding the return_record_info parameter to the correct base class please.
• Should I also apply this pattern to ProtobufDeserializer and JSONDeserializer for consistency?
• I plan to apply the same logic to the _async path once the sync implementation is approved.

[confluent-cla-assistant]

🎉 All Contributor License Agreements have been signed. Ready to merge.
✅ harrold-mussa
_{Please push an empty commit if you would like to re-run the checks to verify CLA status for all contributors.}

[harrold-mussa]

Hello @MSeal !
Could you point me to the correct file to modify the constructor? I've got the core logic working in a draft state.