Missmatch in Min/Max size notation flags a warning

[m-adams]

Readiness Checklist

• [x ] I am running the latest version
• [ x] I checked the documentation and found no answer
• [ x] I checked to make sure that this issue has not already been filed
• [ x] I am reporting the issue to the correct repository (for multi-repository projects)

Expected Behavior

No warnings should be thrown

Current Behavior

I created a cluster with autoscaling and min/max values.
I believe I simply used 0 in the configuration and it looks like the provider returned 0g so terrafrom threw a conflict.

When applying changes to ec_deployment.example, provider
"provider[\"registry.terraform.io/elastic/ec\"]" produced an unexpected new
value: .elasticsearch.ml.autoscaling.min_size: was cty.StringVal("0"), but
now cty.StringVal("0g").

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

## Terraform definition
ml = {
autoscaling = {
min_size = 0
max_size = "32g"
}
}

Steps to Reproduce

1. Deploy a configuration with 0 as the min value