setting min-capacity with az sql db update --min-capacity does not appear to actually set the capacity.

> ### `az feedback` auto-generates most of the information requested below, as of CLI version 2.0.62

**Describe the bug**
I am attempting to use the azure cli to change the min-capacity on a mssql database on an basic sku elastic pool.
I've created the elastic pool with per database settings of min-capacity = 0 and max-capacity = 5.
When I create the sql database through the portal, it creates a sql database with the minCapactiy set to null. When I then try to update that on the azure cli, no matter what value I give for --min-capacity, the resulting output is always "minCapacity": null,

**To Reproduce**
Create sql database in an elastic pool with min-capacity of 0
Attempt to change the min-capacity via the azure cli.
`az sql db update -g fssa-dfr-dev-impact-rg -s fssa-dfr-dev-impact-sqlsvr -n fssa-dfr-dev-impact-db --min-capacity 0.5`

**Expected behavior**
I expect this
`"minCapacity": null,`
to change to
`"minCapacity": 0.5,
`

**Environment summary**

**Additional context**
I'm building out my environment with terraform, but because of various bugs like, [cannot create sql database with terraform](https://github.com/Azure/azure-rest-api-specs/issues/10411) and [issues with terraform and a 0 min-capacity](https://github.com/terraform-providers/terraform-provider-azurerm/issues/8226) I'm trying to find workarounds to import the sql database I must create via the portal and not terraform into my terraform state.