Migrate legacy CAN() permission checks to Sistent useHasPermission hook (Pattern C) - #20860

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ui/components/connections/wizard/genericSteps.tsx`:
- Around line 86-90: The selectStep canProceed guard must enforce kind
permissions for preset/deep-linked connections, not only check that kindConfig
exists. Update selectStep.canProceed to require
kindPermission(ctx.data.kindConfig) alongside the existing presence check,
preserving normal selection behavior while rejecting unauthorized kinds.

In `@ui/components/designs/patterns/MesheryPatterns.tsx`:
- Around line 72-83: Update the permission gate in MesheryPatterns so
catalog-only users authorized by Keys.CatalogManagementViewCatalog are not
rejected by the separate Keys.CatalogManagementViewDesigns check. Pass the
page-specific permission into the shared component or condition the gate on the
active route, while preserving the existing design permission behavior for
design routes.

In `@ui/components/settings/MesherySettings.tsx`:
- Line 255: Gate the registry content rendering, not only its tab control:
update the REGISTRY branch identified by tabVal and MeshModelComponent to
require canViewRegistry, or enforce the equivalent check inside
MeshModelComponent, so direct Registry routes cannot render without permission.

In `@ui/components/shared/Modal/Information/LegacyInfoModal.tsx`:
- Around line 496-501: Update the disabled expression for the “Publish to
Catalog” button in LegacyInfoModal so unpublished designs are enabled only when
canPublishDesign is true and the current user owns the selected resource, while
published designs remain disabled. Remove the swapped ternary branches and
redundant isPublished condition so the permission and ownership checks affect
the result.

In `@ui/components/workspaces/WorkspaceFormModalNav.tsx`:
- Line 50: Update WorkspaceContentWrapper so its getNavItem call passes the
required canViewViews argument, propagating the existing permission value or
retrieving it within the wrapper before building navigation items. Ensure all
getNavItem invocations satisfy its updated signature.

---

Nitpick comments:
In `@ui/components/connections/ConnectionTable.test.tsx`:
- Line 1: The tests only cover permitted states because useHasPermission is
always mocked to return true. Add denied-permission variants in ConnectionTable
tests to verify MultiSelectWrapper and ConnectionStatusSelect are disabled, in
HeaderMenu tests to verify “Get Token” is hidden when hasDownloadTokenPermission
is false, and in InfoModal tests to verify “Publish to Catalog” is disabled when
canPublishDesign is false.

In `@ui/components/dashboard/charts/ConnectionCharts.test.tsx`:
- Line 82: Make all permission mocks key-aware: in
ui/components/dashboard/charts/ConnectionCharts.test.tsx at lines 82-82, forward
the requested key from useHasPermission to canSpy and assert
Keys.WorkspaceManagementViewConnections; in
ui/components/dashboard/charts/DashboardMeshModelGraph.test.tsx at lines 67-67,
replace the unconditional true mock with a spy and assert
Keys.MesherySystemViewRegistry; in
ui/components/settings/MesherySettings.test.tsx at lines 67-67, replace the
shared boolean with a key-aware mapping or spy covering the settings,
infrastructure, and registry permission keys.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ui/components/connections/wizard/useConnectionWizard.tsx`:
- Around line 145-150: Update the preset-handling effect around
appliedPresetRef, data.kindConfig, and kindPermission so permission is confirmed
before consuming the preset or changing wizard state. When permission is denied,
leave the preset unapplied and do not select or advance it; when permission
becomes available later, allow the same preset to be processed and advance to
the kind-details step. Add coverage for denied and delayed-permission scenarios.

In `@ui/components/workspaces/WorkspaceFormModalNav.tsx`:
- Line 100: Update the canViewViews permission checks in WorkspaceContentWrapper
and the related Navigation/getNavItem callers to consistently use
Keys.KanvasViewViews, matching the existing navigation authorization contract
and eliminating use of Keys.CatalogManagementViewViews for My-Views.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ui/components/workspaces/WorkspaceFormModalNav.tsx`:
- Line 151: Update the navigation state around navConfig and selectedId so that
when the currently selected item is no longer present because its permission is
denied, selectedId is reset to the allowed default view (such as Recents).
Preserve the existing selection when the selected navigation item remains
enabled, and ensure the header and displayed content use the reconciled
selection.