windows tests should (1) fail if management cluster is specified (2) accomodate 'prod' clusters

[jayunit100]

Bug description

Lets add several validations to our windows YTT:

• in YTT Right now , any user making a windows cluster shouldnt label it as management, bc we only support windows for workload clusters. Lets add a unit test confirming YTT FAILS if the management cluster is set (b/c you can NEVER have windows nodes in a management cluster)
• for windows clusters, we ALSO want to validate every file injected in the kubeadm post-start (i.e. the new windows reboot prevention patch from @stuartpreston, #977 ), by adding a test to the https://github.com/vmware-tanzu/tanzu-framework/blob/main/pkg/v1/providers/tests/unit/windows_test.go file.

Affected product area (please put an X in all that apply)

• [ ] APIs
• [ ] Addons
• [ ] CLI
• [ ] Docs
• [ ] IAM
• [ ] Installation
• [ ] Plugin
• [ ] Security
• [ ] Test and Release
• [ x ] User Experience

Expected behavior

The windows cluster creation is smart enough to short circuit in cases where other parameters are non compatibly such as this one.

Steps to reproduce the bug

Make a windows ytt template with IS_WINDOWS_CLUSTER true, but set it to type management.

[jayunit100]

/assign

[jayunit100]

/good-first-issue

[jayunit100]

• add cluster_plan=prod to the unit tests
• allow 4 machine templates instead of 2
• confirm that MANAGEMENT_CLUSTER fails if IS_WINDOWS=true