change: [M3-10586] - Remove update strategy from node pool summary item in LKE checkout bar

[mjac0bs]

Description 📝

Currently, with Post LA changes, the kube checkout bar was updated to show the node pool's update strategy for each pool (for LKE-E clusters, where this selection is available).

After UX feedback, we've decided to keep the information in the checkout bar simple to avoid overwhelming the user with too many details and focus on pricing. Update strategy and firewall will not be listed.

Firewall was not added to begin with, I just forgot to remove update strategy earlier - since this is only a display change and has no functional impact, I don't think it's priority to squeeze this into the already cut 9/9 release, even if we flip the post LA flag before 9/23.

Changes 🔄

• Remove the displayed update strategy from the UI and clean up related RHF logic no longer needed

Scope 🚢

Upon production release, changes in this PR will be visible to:

• All customers
• Some customers (e.g. in Beta or Limited Availability)
• No customers / Not applicable

Target release date 🗓️

9/23

Preview 📷

Before	After

How to test 🧪

Prerequisites

• Have LKE-Enterprise enabled (feature flags: enabled, la, postLa) + customer tag

Reproduction steps

(How to reproduce the issue, if applicable)

• Check out develop and go to http://localhost:3000/kubernetes/create
• Select an LKE-E tier, go through the create flow, and add at least one node pool to the cluster
• Observe the checkout bar and note the update strategy is listed

Verification steps

(How to verify changes)

• Check out this branch
• Select an LKE-E tier, go through the create flow, and add at least one node pool to the cluster
• Observe the checkout bar and note the update strategy is not listed

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 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

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

[bnussman-akamai]

I like this better. Nice