Error out if no subnets found

[JacobGabrielson]

1. Issue, if available:

N/A

2. Description of changes:

Before, if zero subnets were found (via the tag), the controller would continue on, even though there is no way for it to launch any instances. Now it errors with a message like:

2021-11-16T16:55:19.034Z	ERROR	controller.controller.Allocation	Reconciler error	{"commit": "53cd6c4", "reconciler group": "karpenter.sh", "reconciler kind": "Provisioner", "name": "default", "namespace": "", "error": "getting instance types, no subnets found via [{\"Name\":\"tag-key\",\"Values\":[\"kubernetes.io/cluster/foo-karpenter-demo.us-west-2.eksctl.io\"]}]"}

3. Does this change impact docs?

• Yes, PR includes docs updates
• Yes, issue opened: link to issue
• No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[netlify]

✔️ Deploy Preview for karpenter-docs-prod canceled.

🔨 Explore the source changes: dde182f

🔍 Inspect the deploy log: https://app.netlify.com/sites/karpenter-docs-prod/deploys/6193e44fcf680b00071e06ea

[ellistarn]

Can you reference something like spec.provider.subnetSelector= so the user knows where to look?

[bwagner5]

lgtm