Fixed bug in aws cloudprovider where API machinery IsNotFound was incorrectly used on ec2 Terminate resp

[bwagner5]

Issue, if available:
N/A

Description of changes:

• Fixes a bug where API Machinery errors.IsNotFound() was being used to evaluate the error response from an AWS sdk call to EC2. The specific call is checking if the TerminateInstances API returns an "Instance ID does not exist" error which would indicate that the instance was already terminated or for whatever other reason, no longer exists. In this case, Karpenter should move along and delete the nodes from the k8s API server.

TLDR:
The logic was correct, but the wrong error check was used which caused nodes to hang when the ec2 instance had already been termianted.

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: 39f1108

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

[ellistarn]

Related to #549?

[ellistarn]

Nice!

[bwagner5]

Related to #549?

I think that is a different issue. I suspect you're correct about the NodeName == ""

[njtran]

lgtm