Fix: Map diagram showing resources from other namespaces

[tejhan]

Description

This PR adds a namespace guard to makeRelation so that for namespace-scoped resources, edges are only drawn if they're in the same namespace. Previously we only matched by name/label, causing resources with identical names in different namespaces to be merged and shown under one namespace component in the view.

Resolves issue

• [BUG] Map diagram includes resources from other namespace #621

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Performance improvement
• Code refactoring
• CI/CD changes
• Other: **___**

Related Issues

Closes #621

Changes Made

• Added namespace equality check in makeRelation to prevent cross-namespace edges being drawn for identically named resources.

Testing

• Unit tests pass
• Integration tests pass
• Manual testing completed
• Performance tested (if applicable)
• Accessibility tested (if applicable)

Test Cases

Describe the test cases that were run:

1. Create 2 deployments/resources with identical names.
2. Open the Map view & observe that the deployments for one namespace don't appear in another.

[Copilot]

Pull request overview

This PR fixes the Resource Map’s relation-building logic to avoid drawing edges between namespace-scoped resources that happen to share the same name/labels across different namespaces, which previously caused cross-namespace resources to appear/merge when filtering by namespace.

Changes:

• Added a namespace equality guard inside makeRelation so relations only connect namespaced objects within the same namespace.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[gambtho]

lgtm