APIT-2883: Release a fix for the issue #619

[Kostya Linou (linouk23)]

Release Notes

Bug Fixes

• Fixed "Persistent terraform drift when creating a confluent_schema that already existed as one of the previous versions" issue (CLI-3508: Persistent terraform drift when creating a confluent_schema that already existed as one of the previous versions #619).

Checklist

WIP

• I can successfully build and use a custom Terraform provider binary for Confluent.
• I have verified my PR with real Confluent Cloud resources in a pre-prod or production environment, or both.
• I have attached manual Terraform verification results or screenshots in the Test & Review section below.
• I have included appropriate Terraform acceptance or unit tests for any new resource, data source, or functionality.
• I confirm that this PR introduces no breaking changes or backward compatibility issues.
• I have updated the corresponding documentation and include relevant examples for this PR.
• I have indicated the potential customer impact if something goes wrong in the Blast Radius section below.
• I have put checkmarks below confirming that the feature associated with this PR is enabled in:
  • Confluent Cloud prod
  • Confluent Cloud stag
  • Check this box if the feature is enabled for certain organizations only

What

This PR fixes #619 by hardcoding force creating a new version of schema in schemaCreate() method by hardcoding version = -1 in https://docs.confluent.io/platform/current/schema-registry/develop/api.html#post--compatibility-subjects-(string-%20subject)-versions, so SR ensures that the schema differs from all previous versions, causing a new version to be created.

Blast Radius

• Confluent Cloud customers who are creating confluent_schema resources will be blocked.

References

• CLI-3508: Persistent terraform drift when creating a confluent_schema that already existed as one of the previous versions #619

Test & Review

WIP

[Kostya Linou (linouk23)]

Update: we encounter an issue when testing this PR, see #619 (comment) for more details and the workaround, thank you!