Specifying 'disabled' for '--endpoint-status' creates an endpoint in the 'Enabled' state

[nwohlgemuth]

Describe the bug
The '--endpoint-status' argument value of 'az network traffic-manager endpoint create' is case sensitive and does not behave the way one would expect. If 'Disabled' is specified as the value, the new endpoint has 'Disabled' as the status. If 'disabled' is specified, the new endpoint has 'Enabled' as the status.

To Reproduce
Create a new traffic manager endpoint using 'az network traffic-manager endpoint create' and specify '--endpoint-status disabled' as one of the arguments. Observe that the newly created endpoint is in the 'Enabled' state even though 'disabled' was requested.

Expected behavior
Specifying an invalid value for the endpoint status such as 'invalid' will cause the Azure CLI to print the message that the only valid values are 'Enabled' and 'Disabled'. But the CLI will accept 'disabled' as a value but then treat it as if it was actually 'Enabled'. Either the CLI should reject 'disabled' as invalid or it should accept it and treat it as 'Disabled'.

Environment summary
Azure CLI 2.0.33 on both Windows and Linux