Remove Go to Console link from root organization actions and show a URL instead

[brionmario]

Purpose

There are issues in having a Go to Console link and we can't properly workaround this without first resolving wso2/product-is#22615

This pull request focuses on removing the Go to Console link from root organization actions and replacing it with a URL display. The changes span multiple files and include updates to components, hooks, context, styles, and i18n translations. Here are the most important changes:

Removal of Go to Console link:

• features/admin.tenants.v1/components/tenant-card.tsx: Removed the navigateToTenantConsole function and related UI elements. [1] [2]
• features/admin.tenants.v1/context/tenant-context.tsx: Removed the navigateToTenantConsole function from the context. [1] [2]
• features/admin.tenants.v1/providers/tenant-provider.tsx: Removed the logic and state related to tenant console navigation. [1] [2] [3] [4] [5]

Addition of URL display for console:

• features/admin.tenants.v1/hooks/use-tenant-console-url.ts: Added a new hook to generate the console URL for a given tenant.
• features/admin.tenants.v1/pages/edit-tenant-page.tsx: Updated the edit tenant page to display the console URL with a copy button. [1] [2] [3] [4] [5]
• features/admin.tenants.v1/pages/edit-tenant-page.scss: Added styles for the console URL display.

i18n updates:

• modules/i18n/src/models/namespaces/tenants-ns.ts: Removed navigatingToTenantConsole translations and added translations for the console URL. [1] [2]
• modules/i18n/src/translations/en-US/portals/tenants.ts: Updated the English translations to reflect the removal of Go to Console and addition of console URL.

Documentation and metadata:

• .changeset/fast-nails-nail.md: Documented the removal of the Go to Console link and the reason behind it.

Related Issues

• Error Page Displayed When Accessing 'Go to Console' Option in Root Organization product-is#22225

Related PRs

• N/A

Checklist

• e2e cypress tests locally verified. (for internal contributers)
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Relevant backend changes deployed and verified
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines
• Ran FindSecurityBugs plugin and verified report
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.98%. Comparing base (f7338ef) to head (91f48a3).
Report is 89 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7490   +/-   ##
=======================================
  Coverage   41.98%   41.98%           
=======================================
  Files          42       42           
  Lines         936      936           
  Branches      214      214           
=======================================
  Hits          393      393           
  Misses        543      543           

Flag	Coverage Δ
@wso2is/core	41.98% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[pavinduLakshan]

shall we use a SCSS variable for the color?

[brionmario]

This is a temporarily thing that needs to be fixed with Oxygen UI.
We should not encourage to re-use a variable. So, lets link and issue here instead.

[pavinduLakshan]

instead of removing the impl., shall we hide/disable the feature so that it can be enabled once the cookie issues are fixed?

[wso2-jenkins-bot]

🦋 Changeset detected

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

[brionmario]

instead of removing the impl., shall we hide/disable the feature so that it can be enabled once the cookie issues are fixed?

An issue is created to restore the link once the backend problems are resolved.

The above backend issue might take some time to implement, so its better to not keep stale code if we can't immediately bring them back.

Mainly since Console is a quite large application and a single line of code takes Bites from the bundle.

• Add the Go to Console button back in the Root Organizations feature once the cookie path issue is fixed product-is#22784