Add Confluent-Client-Version header to requests to SR, Golang client

[fangnx]

What

Checklist

• Contains customer facing changes? Including API/behavior changes
• Did you add sufficient unit test and/or integration test coverage for this PR?
  • If not, please explain why it is not required

References

JIRA: https://confluentinc.atlassian.net/browse/DGS-22770

Test & Review

Open questions / Follow-ups

[Copilot]

Pull request overview

This PR adds the Confluent-Client-Version header to Schema Registry REST API requests. The version format is "go/{version}" where the version is derived from the librdkafka library version.

• Introduces a new helper function to generate the client version header value
• Sets the Confluent-Client-Version header during REST service initialization

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The comment states the version is 'tied to the librdkafka version', but this coupling may be confusing since this is a Schema Registry client. Consider clarifying why the librdkafka version is used for the Schema Registry client version header, or if a dedicated Schema Registry client version should be used instead.

Suggested change

	// getClientVersionHeaderValue returns the client version header value
	// in the format "go/{version}"
	// Note: currently the client version is tied to the librdkafka version
	func getClientVersionHeaderValue() string {
	_, version := kafka.LibraryVersion()
	return "go/" + version
	// getClientVersionHeaderValue returns the Schema Registry client version header value
	// in the format "go/{version}"
	// Note: this version reflects the Schema Registry client, not the Kafka library version.
	const schemaRegistryClientVersion = "1.0.0" // TODO: Update this version as needed for releases
	func getClientVersionHeaderValue() string {
	return "go/" + schemaRegistryClientVersion

[sonarqube-confluent]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[rayokota]

Can we avoid the dependency of the SR client on Kafka?