[Bug]: Opensearch version produced inconsistent result after apply

[K987]

Current Behavior

After provisioning an Opensearch cluster of default version of 3.3 the returned version number is 3.

Note: 3 is not a valid version value:

This raises an error after the resource was provisioned:

It eventually marks the resource as tainted after creation in terraform, and unless the opensearch.version is not marked as ignored in the lifecycle block, it would force recreation on each terraform run.

Expected Behavior

When the opensearch.version attribute is set to 3.3, then the same value is returned from the resource upon creation.

Steps To Reproduce

1. Define an opensearch dbaas service in terraform, set the attribute opensearch.version to 3.3
2. Create the resource

Provider Version

0.66.0

Terraform Version

1.14.3"

Relevant log output

module.opensearch.exoscale_dbaas_opensearch_user.sks_user: Creating...
module.opensearch.exoscale_dbaas.opensearch: Creating...
module.opensearch.exoscale_dbaas_opensearch_user.sks_user: Creation complete after 3s [id=auth-prd-03-opensearch/sks_user]
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.opensearch.exoscale_dbaas.opensearch, provider
│ "provider[\"registry.terraform.io/exoscale/exoscale\"]" produced an unexpected new value: .opensearch.version: was
│ cty.StringVal("3.3"), but now cty.StringVal("3").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵