fix: [M3-7706, 9005] - Set VPC interface as primary when creating a Linode

[coliu-akamai]

Description 📝

Sets VPC interfaces as the primary interface when creating a Linode - this had been lost in the refactor.

See internal ticket 7706 for details of investigation. This does not resolve the unrecommended config notice for already existing Linodes, just for newly created ones. Customers with this notice on their Linode will need to manually edit their configs to resolve it.

The bug with the Linode Config Dialog should be resolved in #11424

Target release date 🗓️

1/14

Preview 📷

Before	After

How to test 🧪

Reproduction steps

• Create a Linode (assign it to a VPC in the creation flow)
• Note how inside the VPC, the Linode has an 'unrecommended config' notice

Verification steps

• Following the same steps above, confirm that a newly created Linode will not have unrecommended config notice
• Confirm that any time a Linode is created with a VPC interface, the VPC interface will be marked as primary (test with/without Vlans and private IPs)

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

[coliu-akamai]

neither publicInterface nor vlanInterface were marked as primary previously, and in the API spec linked in internal ticket 7706 notes that vlans cannot be the primary interface

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #4 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	471 Passing	2 Skipped	116m 56s

Details

Failing Tests
	Spec	Test
❌	clone-linode.spec.ts	clone linode » can clone a Linode from Linode details page

Troubleshooting

Use this command to re-run the failing tests:

yarn cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts"