Fix issue with side nav losing highlight for some routes

[rak-phillip]

Summary

This resolves an issue where some routes would lose their highlight and would collapse the containing group when active.

Fixes #18495

Occurred changes and/or fixed issues

• Add navResources option to type-map
• Move isActive() logic into router utils

Technical notes summary

Two issues were identified during triage:

1. Certain generic routes are expected to behave as children for resources. For example, listing Projects/Namespace has an active route of /c/local/explorer/projectsnamespaces, but creating a Project has an active route of /c/local/explorer/management.cattle.io.project/create#members. The create pages will never match a nav entry in this event.
2. Some routes like creating cluster drivers have exact: true specified. In these cases, the list route is /c/_/manager/kontainerDriver and the create route is /c/_/manager/kontainerDriver/create. The create page is a direct child of, but will never match the nav item because it requires an exact route match to be marked as active.

Areas or cases that should be tested

The affected areas were identified during triage:

• Cluster explorer
  • Projects/Namespace
    • Create Namespace
    • Create Project
  • Cluster and Project Members
    • Add
• Cluster Management
  • Providers
    • Create Cluster Drivers
    • Create Node Drivers

Areas which could experience regressions

Changing exact to false for existing types could impact some behavior elsewhere. I wasn't able to identify where this could be problematic, but I think that we should be cautious of the change.

Screenshot/Video

Create Namespace

Before

After

Create Cluster Driver

Before

After

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[marcelofukumoto]

Before	After

Recording:

record.webm

Just some tests done.

[marcelofukumoto]

Some questions and Nit
From my automated and manual tests it seems good.

[aalves08]

@rak-phillip seems to be working as claimed, even with the new product registration API. Just missing Marcelo's comments.

[marcelofukumoto]

LGTM