feat: [M3-7358] - Add AGLB Feedback Link

[cpathipa]

Description 📝

Add AGLB Feedback Link.

Before	After

How to test 🧪

Verification steps

(How to verify changes)

• Navigate to http://localhost:3000/loadbalancers.
• Verify Feedback link in all AGLB pages.
• Verify LandingHeader Docs link alignment across the CM.
• Link should navigate to google forms in a new tab.

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

[cpathipa]

IMO, ExternalLinkIcon makes more sense here. Since its navigating users from CM. But, needs confirmation from UX.

[abailly-akamai]

We already have an external link icon on the component but you hide it to add another one. why not just use our component treatment? (or the proper docs link treatment)

{feedbackLink && (
          <Grid container sx={docsLink ? sxFeedbackLink : null}>
            <Link external to={feedbackLink}>
              {feedbackLinkLabel}
            </Link>
          </Grid>
        )}

Also, you don't really need a Typography around the Link.

[mjac0bs]

@cpathipa - You might have already mentioned this to UX, but can we maintain consistent styling across our products in beta? VPC looks a little different in #9879.

[cpathipa]

@cpathipa - You might have already mentioned this to UX, but can we maintain consistent styling across our products in beta? VPC looks a little different in #9879.

@mjac0bs I'm not aware of this PR, I will make the Icon changes consistent with VPC feedback link.

[abailly-akamai]

We already have an external link icon on the component but you hide it to add another one. why not just use our component treatment? (or the proper docs link treatment)

{feedbackLink && (
          <Grid container sx={docsLink ? sxFeedbackLink : null}>
            <Link external to={feedbackLink}>
              {feedbackLinkLabel}
            </Link>
          </Grid>
        )}

Also, you don't really need a Typography around the Link.

[cpathipa]

@abailly-akamai My initial thought was to maintain a separation of concerns, which is why I chose to implement a separate code block for the feedback component. This decision resulted in hiding the default icon that appears after the link text. However, our requirement was to display the icon before the link text. Additionally, I was not aware of #9879 that might have addressed this.

[tyler-akamai]

Verified:

• Feedback link appears in all AGLB pages.
• LandingHeader Docs link has proper alignment across CM
• Link navigates to google forms in a new tab

[jaalah-akamai]

Thanks for aligning this with our previous design

[mjac0bs]

Confirmed link styling is consistent with VPC BETA Feedback and the feedback link displays on the Landing, Details, and Create pages. ✅

Styling edge case:

Screenshots

Can we add some left margin for mobile view? When the link wraps on the smallest screens, it could be in line with the Breadcrumb.

[cpathipa]

@mjac0bs Added left margin for small screen. 33c441d