fix: [M3-7059] - Stop resetting count and disabling Add button when adding node pool to Kubernetes cluster

[mjac0bs]

Description 📝

🐛 On the cluster creation page, if you remove an added node pool from the cluster summary, that plan in the node pool does not become re-enabled.

Fix: This was happening because the number of node pools in the map was being reset to 0 when a node pool was added to a cluster. When the number input is 0, the add button is disabled. We should not reset the number of node pools to 0 once it has been added to the pool.

Changes 🔄

List any change relevant to the reviewer.

• Removed the call to updatePlanCount in the handler for adding a node pool to a cluster.

Preview 📷

Before	After
Screen.Recording.2024-02-21.at.2.28.21.PM.mov	Screen.Recording.2024-02-21.at.2.28.54.PM.mov

How to test 🧪

Prerequisites

Reproduction steps

(How to reproduce the issue, if applicable)

1. In prod, go to the Create Cluster page.
2. Click the Add button for a plan in the node pools table. That Add button is now disabled.
3. In the Cluster Summary section, click the X to remove that node pool. The Add button for that plan stays disabled.

Verification steps

(How to verify changes)

1. Check out this PR and go to the Create Cluster page.
2. Click the Add button for a plan in the node pools table. That Add button remains enabled and the number input is not reset to 0; instead, it remains the same as whatever the user last input.
3. Verify the correct number of nodes and pricing shows up in the Cluster Summary, then remove the node pool from the cluster summary.
4. Confirm that the Add button remains enabled with the same number of nodes as whatever the user last input.
5. The behavior should be the same in mobile view with the selection cards.
6. Confirm kube e2es still pass.

As an Author I have considered 🤔

Check all that apply

• 👀 Doing a self review
• ❔ Our contribution guidelines
• 🤏 Splitting feature into small PRs
• ➕ Adding a changeset
• 🧪 Providing/Improving test coverage
• 🔐 Removing all sensitive information from the code and PR description
• 🚩 Using a feature flag to protect the release
• 👣 Providing comprehensive reproduction steps
• 📑 Providing or updating our documentation
• 🕛 Scheduling a pair reviewing session
• 📱 Providing mobile support
• ♿ Providing accessibility support

[github-actions]

Coverage Report: ✅
Base Coverage: 81.33%
Current Coverage: 81.33%

[jdamore-linode]

Nice, thanks @mjac0bs for the explanation and detailed reproduction/verification tests!

[bnussman-akamai]

OMG! This reminds me of some feedback (#7654 (review)) I got on one of my first PRs I did at Linode 🥺

I think in the past we made it reset to 0 so that mobile users had some kind of indication that something actually happened, but I think this change is still fine.