Set-CustomDRS is setting TryBalanceVmsPerHost to 0 and it shouldn't

Found in this commit:

_Originally posted by @jlinenkohl in [e6ed72d](https://github.com/Azure/Microsoft.AVS.Management/commit/e6ed72da894c86200da3b0a1f9f9583212bdad0c#r198465520)_
--

> This option, "TryBalanceVmsPerHost" should not be here. Also, IsClusterManaged is already set by default, so not including it here is OK. Retaining it is also OK.
>
>
>
References:

[Powering on a VM fails with Error "Insufficient Resources"](https://knowledge.broadcom.com/external/article/398993/powering-on-a-vm-fails-with-error-insuff.html)

[vsphere-vcenter-server-650b-release-notes.pdf](https://techdocs.broadcom.com/content/dam/broadcom/techdocs/us/en/pdf/vmware/vsphere/vsphere/vSphere-6-5-Release-Notes/vsphere-vcenter-server-650b-release-notes.pdf)
>
>
>
>

Start at the Set-CustomDRS entry point and trace how the TryBalanceVmsPerHost option is assigned. Confirm the change prevents this setting from being written as 0, while preserving the existing IsClusterManaged behavior, then verify the resulting DRS configuration against the referenced VMware guidance.

Written by the indexing model from the issue text.