[machineops] Deploy machine ops by default in site init

[Israel Miller (imiller31)]

Summary

• install machine-ops-controller by default from kubectl unbounded site init, including embedded manifests and --machine-ops-manifests
• inject the cluster API server endpoint into machine-ops manifests, including custom multi-document YAML bundles
• update AKS quickstart, release, release-upgrade, local release validation, and docs so machine-ops is covered end to end

Validation

• go test ./cmd/kubectl-unbounded/app
• make test
• bash -n hack/test-release-local.sh hack/test-goreleaser-hook.sh
• PATH="$PWD/tmp/bin:$PATH" goreleaser check
• PATH="$PWD/tmp/bin:$PATH" ./hack/test-goreleaser-hook.sh
• live AKS quickstart setup with local Azure account; verified machine-ops rollout, endpoint arg, RBAC, logs, and cleaned up the resource group

Notes

• GoReleaser was installed locally at tmp/bin/goreleaser for release-hook validation.