refactor: [M3-8777] - Refactor CreateCluster component to use react-hook-form

[hasyed-akamai]

Description 📝

Highlight the Pull Request's context and intentions.

Changes 🔄

List any change(s) relevant to the reviewer.

• ...
• ...

Target release date 🗓️

Please specify a release date (and environment, if applicable) to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.

Preview 📷

Include a screenshot or screen recording of the change.

🔒 Use the Mask Sensitive Data setting for security.

💡 Use <video src="" /> tag when including recordings in table.

Before	After
📷	📷

How to test 🧪

Prerequisites

(How to setup test environment)

• ...
• ...

Reproduction steps

(How to reproduce the issue, if applicable)

• ...
• ...

Verification steps

(How to verify changes)

• ...
• ...

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 unit tests are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules

---

Commit message and pull request title format standards

Note: Remove this section before opening the pull request
Make sure your PR title and commit message on squash and merge are as shown below

<commit type>: [JIRA-ticket-number] - <description>

Commit Types:

• feat: New feature for the user (not a part of the code, or ci, ...).
• fix: Bugfix for the user (not a fix to build something, ...).
• change: Modifying an existing visual UI instance. Such as a component or a feature.
• refactor: Restructuring existing code without changing its external behavior or visual UI. Typically to improve readability, maintainability, and performance.
• test: New tests or changes to existing tests. Does not change the production code.
• upcoming: A new feature that is in progress, not visible to users yet, and usually behind a feature flag.

Example: feat: [M3-1234] - Allow user to view their login history

---

[linode-gh-bot]

Cloud Manager UI test results

🔺 8 failing tests on test run #2 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
8 Failing	480 Passing	2 Skipped	126m 3s

Details

Failing Tests
	Spec	Test
❌	lke-create.spec.ts	LKE Cluster Creation » can create an LKE cluster
❌	lke-create.spec.ts	LKE Cluster Creation with APL enabled » can create an LKE cluster with APL flag enabled
❌	lke-create.spec.ts	with LKE IPACL account capability » creates an LKE cluster with ACL disabled
❌	lke-create.spec.ts	with LKE IPACL account capability » creates an LKE cluster with ACL enabled
❌	lke-create.spec.ts	with LKE IPACL account capability » can handle validation and API errors
❌	smoke-lke-create.spec.ts	LKE Create Cluster » Simple Page Check
❌	plan-selection.spec.ts	displays kubernetes plans panel based on availability » displays the proper plans based on the region and types
❌	plan-selection.spec.ts	displays specific kubernetes plans for GPU » Should render divided tables when GPU divider enabled

Troubleshooting

Use this command to re-run the failing tests:

yarn cy:run -s "cypress/e2e/core/kubernetes/lke-create.spec.ts,cypress/e2e/core/kubernetes/smoke-lke-create.spec.ts,cypress/e2e/core/linodes/plan-selection.spec.ts"