docs: Clarify NodePool disruption budgets impact on drift reconciliation

[josh-ferrell]

Fixes #7036

Description
Clarify that NodePool disruption budgets can prevent NodeClaim termination when the reason is drift. Expiration is verified as unaffected by disruption budgets.

How was this change tested?
Four NodePools were created with a combination of budgets with nodes set to 0 or 10% and with reasons let unspecified, reasons set to Empty only and reasons set to Drifted only. NodePool disruption budgets with nodes set to 0 and without reasons given or with the reason Drifted given prevented nodeclaim termination after changing the AMI in the underlying EC2NodeClass. As an example the following budgets would prevent nodeclaim termination between 12AM - 12PM UTC for any reason, nodeclaim termination because of drift anytime and would allow nodeclaim termination when empty for 10% of the nodepool at a time.

budgets:
  - nodes: 10%
    reasons:
      - Empty
  - nodes: "0"
    reasons:
      - Drifted
  - duration: 12h0m0s
    nodes: "0"
    schedule: 0 12 * * mon-fri

Does this change impact docs?

• Yes, PR includes docs updates
• Yes, issue opened: #
• 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 ready!

Name	Link
🔨 Latest commit	bb82a66
🔍 Latest deploy log	https://app.netlify.com/sites/karpenter-docs-prod/deploys/67508969d8b66700084d15f9
😎 Deploy Preview	https://deploy-preview-7483--karpenter-docs-prod.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coveralls]

Pull Request Test Coverage Report for Build 12164529859

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 65.022%

---

Totals
Change from base Build 12147487832:	0.0%
Covered Lines:	5733
Relevant Lines:	8817

---

💛 - Coveralls