Update release testing process with recent changes
The VM CRD is so big that we can't use `kubectl apply`.
The `deploy_testing_secret` script now has a mode that handles AAD pod identity.
2. Create a kind cluster: `task controller:kind-create`
3. Install cert-manager: `task controller:install-cert-manager`
4. Create the namespace for the operator: `k create namespace azureserviceoperator-system`
-5. Source the SP credentials to use for the secret and then run `./scripts/deploy_testing_secret.sh`
-6. Deploy the operator from MCR: `k apply -f <path-to-downloaded-yaml>`
+5. Source the SP credentials to use for the secret and then run `./scripts/deploy_testing_secret.sh sp`
+6. Deploy the operator from MCR: `k create -f <path-to-downloaded-yaml>` (We can't use `apply` because the yaml for VirtualMachines is too large - it can't be stored in the `last-applied-configuration` annotation.)
7. Wait for it to start: `k get all -n azureserviceoperator-system`
8. Create a resource group: `k apply -f v2/config/samples/microsoft.resources/v1alpha1api20200601_resourcegroup.yaml`
9. Make sure it deploys successfully, and check in the portal.
