feat(frontend): link Artifact Validator checks to their CoreArtifactDefinition

[iddocohen]

Summary

• In the Proposed Change "Checks" tab, each CoreArtifactValidator accordion now shows a small "open in new" icon link that navigates to the originating CoreArtifactDefinition. The same link is also added as a "Definition" row in the validator details popover.
• This addresses user feedback that there was no way to navigate from an Artifact Validator check (e.g. "Artifact Validator: MachineConfig_Artifact_Definition") back to the definition that produced it without copy-pasting the name and finding it manually under objects/CoreArtifactDefinition.

What changed

• frontend/app/src/entities/diff/api/get-validators-from-api.ts — extended the GET_CORE_VALIDATORS query with an inline fragment on CoreArtifactValidator to fetch definition { node { id, display_label, __typename } }.
• frontend/app/src/entities/diff/ui/checks/validator.tsx — when the validator is a CoreArtifactValidator, render a Link to CoreArtifactDefinition/<id> in the accordion header (with stopPropagation so it does not toggle the accordion) and add a "Definition" row to the info popover.
• frontend/app/src/shared/api/graphql/generated/graphql-cache.d.ts — regenerated via gql.tada generate turbo to reflect the new query shape.

No backend changes. The CoreArtifactValidator.definition relationship is already defined in the schema (backend/infrahub/core/schema/definitions/core/propose_change_validator.py) and populated at validator-creation time (backend/infrahub/proposed_change/tasks.py).

Test plan

• Open a Proposed Change that ran at least one Artifact Validator.
• In the "Checks" tab, confirm the corresponding accordion shows the "open in new" icon next to the validator name.
• Click the icon — verify it navigates to the CoreArtifactDefinition detail page and does NOT expand/collapse the accordion.
• Open the validator info popover (ⓘ) — confirm a "Definition" row is present and links to the same definition.
• Confirm non-Artifact validators (Data, Repository, Generator, Schema, User) still render normally with no link or extra popover row.

---

Summary by cubic

Add direct links from CoreArtifactValidator entries in the Proposed Change “Checks” tab to their CoreArtifactDefinition. Users can open the definition from the header icon or a “Definition” row in the details popover.

• New Features

  • Extended GET_CORE_VALIDATORS to fetch definition.node { id, display_label } for CoreArtifactValidator.
  • Render a non-toggling “open in new” link in the accordion header and a “Definition” link in the popover; other validator types are unchanged.

• Refactors

  • Adjusted import order and JSX formatting in validator.tsx to satisfy formatter rules; no behavior changes.

^{Written for commit 719218f. Summary will update on new commits.}

[cubic-dev-ai]

0 issues found across 1 file (changes from recent commits).

<sub>Shadow auto-approve: would auto-approve. This PR adds a frontend-only navigation link from artifact validator checks to their originating artifact definitions, extending an existing GraphQL query with a pre-existing relationship and conditionally rendering a link and popover row; these changes are isolated to the UI, have no backend...

Re-trigger cubic</sub>

[cubic-dev-ai]

No issues found across 4 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would auto-approve. This change adds a navigation link from artifact validators to their definition, using a small GraphQL fragment and existing UI components, with no backend or core logic changes.

Re-trigger cubic</sub>