fix: [UIE-9523] - Show edit RDNS button for VPC NAT IPv4 address row in linode network tab

[grevanak-akamai]

Description 📝

Under linode network tab, edit button is hidden currently for VPC NAT IPv4 address. As part of this PR, this issue is fixed by showing the button for such IP address row.

Changes 🔄

• Updated logic to show/hide edit button in IP address row under linode network tab to show the button for VPC NAT IP address as well.

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 🗓️

December 2025

Preview 📷

Before	After

How to test 🧪

Prerequisites

• Login to https://cloud.devcloud.linode.com/ or https://cloud.linode.com
• Navigate to linodes page

Reproduction steps

• Create Linode
• Create VPC
• Assign linode to VPC. Ensure "Allow public IPv4 access (1:1 NAT)" is checked before assigning Linode to VPC
• Reboot Linode
• After reboot is completed, switch to network tab under linode details page and under IP addresses table, see that IP address row with type "VPC NAT – IPv4" doesn't have edit RDNS button.

Verification steps

(How to verify changes)

• Follow above steps and ensure Edit RDNS button is shown for IP address row with type "VPC NAT – IPv4".
• Ensure no regressions

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

[harsh-akamai]

Changes look good! Thanks @grevanak-akamai