frontend: Handle CRDs with identical plural names

[pablogarciamiranda]

Summary

This PR fixes the routing conflict that occurs when multiple Custom Resource Definitions (CRDs) have the same plural name but belong to different API groups.

Related Issue

Fixes #3778

Changes

• Added group parameter to CRD routes
• Updated components to use {plural}.{group} format for CRD identification
• Modified CRD list to show API group in parentheses
• Fixed navigation links to include both group and plural name

Steps to Test

1. Create two CRDs with the same plural name but different groups
2. Navigate to the CRDs list
3. Click on each CRD and verify correct resources are shown
4. Check that navigation between CRDs works properly

Screenshots (if applicable)

Notes for the Reviewer

• Backwards compatible with existing CRDs
• Group now visible in CRD list for better identification

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pablogarciamiranda / name: Pablo García Miranda (37ba09d)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pablogarciamiranda
Once this PR has been reviewed and has the lgtm label, please assign illume for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @pablogarciamiranda!

It looks like this is your first PR to kubernetes-sigs/headlamp 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/headlamp has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[sniok]

Correct me if I'm wrong but the group is already included in the CRD name, so I'm not sure if this change is needed.

Could you share a more detailed way to reproduce a problem you're experiencing? The issue number you included in the description just points to this PR

[skoeva]

looks like there's also a few tests in the CI failing, would be good to address those

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.