add provisioner taints to nodes

[bwagner5]

1. Issue, if available:
N/A

2. Description of changes:
Taints configured on the provisioner were not being added to nodes provisioned by the provisioner. Now they are being added.

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: 4ad7a91

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

[ellistarn]

Bad merge? I'm adding tests for this in my node affinity PR.

[bwagner5]

Just to add more context to this:

1. Taints are ideally added in two places, once in the allocation controller and once in the cloudprovider's node bootstrap script (userdata for aws). If you're using a custom LaunchTemplate, then the taints don't get added to userdata, and the allocation controller taints were not being added (this PR fixes that).

2. The tests passed because the cloudprovider mock was adding taints. I'm assuming this was added to the mock because userdata is expected to run to add the taints, but like mentioned in 1, we can't necessarily rely on that if a custom launch template is used.