feat(heureka): add Mitigate Manually action to vulnerability rows

[hodanoori]

Summary

Adds a Mitigate Manually action to both the Active and Remediated vulnerability tabs, completing the remediation epic. Users can now mark a CVE as manually mitigated directly from the popup menu on any vulnerability row. The CVE moves to the Remediated tab immediately (optimistic cache update), and can be reverted via the Remediation History Panel.

Changes Made

• Added MitigateManuallyModal component (mirrors FalsePositiveModal, submits type: RemediationTypeValues.Mitigation)
• Added "Mitigate Manually" popup menu item to IssuesDataRow (Active tab) with handleMitigateManuallyConfirm handler
• Added "Mitigate Manually" popup menu item to RemediatedIssueDataRow (Remediated tab) reusing existing handleRemediationConfirm
• Threaded onMitigateManuallySuccess callback through IssuesDataRows → VulnerabilitiesTabContent → ImageIssuesList
• Added success banner: "Vulnerability <CVE> has been manually mitigated and moved to the Remediated list."
• Updated handleRemediatedTabRemediationSuccess to produce correct label for Mitigation type

Related Issues

• Epic: closes [EPIC](heureka): Support "Manual Mitigation" Remediation Type #1659
• Task: closes [Task](heureka): Add manual mitigation action to the list of actions in the Activated Vulnerabilities tab #1660
• Task: closes [Task](heureka): Implement manual mitigation action, modal, and vulnerability state update between tabs #1661
• Task: closes [Task] (heureka): Revert manual mitigation and update vulnerability status #1662

Screenshots (if applicable)

Testing Instructions

1. pnpm i
2. pnpm TASK

Checklist

• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• I have made corresponding changes to the documentation (if applicable).
• My changes generate no new warnings or errors.
• I have created a changeset for my changes.

PR Manifesto

Review the PR Manifesto for best practises.

[changeset-bot]

🦋 Changeset detected

Latest commit: 0b916e1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@cloudoperators/juno-app-heureka	Patch
@cloudoperators/juno-app-greenhouse	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[Copilot]

Pull request overview

Adds first-class UI support in Heureka’s Image Details vulnerabilities list for creating Manual Mitigation remediations from both the Active and Remediated tabs, including optimistic React Query cache updates and user-facing success banners.

Changes:

• Introduces MitigateManuallyModal to create remediations with type: RemediationTypeValues.Mitigation.
• Adds a “Mitigate Manually” action to row popup menus in both Active (IssuesDataRow) and Remediated (RemediatedIssueDataRow) tables.
• Threads a new success callback through the Active tab rendering chain and updates remediated-tab success messaging to include Mitigation.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
apps/heureka/src/components/Service/ImageDetails/MitigateManuallyModal/index.tsx	New modal component for creating mitigation remediations (description/user/expiration + submit).
apps/heureka/src/components/Service/ImageDetails/ImageIssuesList/RemediatedIssuesDataRows/RemediatedIssueDataRow/index.tsx	Adds mitigation action + modal in the Remediated tab, reusing existing remediation creation handler.
apps/heureka/src/components/Service/ImageDetails/ImageIssuesList/IssuesDataRows/IssuesDataRows.test.tsx	Updates tests to pass the newly required onMitigateManuallySuccess prop.
apps/heureka/src/components/Service/ImageDetails/ImageIssuesList/IssuesDataRows/IssuesDataRow/index.tsx	Adds mitigation action + modal in the Active tab, plus optimistic remediations cache update and success callback.
apps/heureka/src/components/Service/ImageDetails/ImageIssuesList/IssuesDataRows/index.tsx	Threads onMitigateManuallySuccess down to IssuesDataRow.
apps/heureka/src/components/Service/ImageDetails/ImageIssuesList/index.tsx	Wires mitigation success banner for Active tab and extends remediated success labeling to include Mitigation.

Comments suppressed due to low confidence (1)

apps/heureka/src/components/Service/ImageDetails/MitigateManuallyModal/index.tsx:115

• MitigateManuallyModal is a new remediation flow but currently has no dedicated Vitest coverage (unlike RiskAcceptanceModal). Consider adding tests that assert: (1) required-field validation (description/userId/expirationDate), (2) onConfirm is called with type=Mitigation and the expected fields (remediatedBy from session vs manual entry, expirationDate ISO), and (3) API errors returned from onConfirm are rendered in the Message banner.

  const handleConfirm = async () => {
    if (!descriptionTrimmed) {
      setDescriptionError("Description is required")
      return
    }
    if (!remediatedBy) {
      setUserIdError("User ID is required")
      return
    }
    if (!expirationDate) {
      setExpirationDateError("Expiration date is required")
      return
    }

    setDescriptionError("")
    setUserIdError("")
    setExpirationDateError("")
    setIsSubmitting(true)
    try {
      const severityValue = severity ? toSeverityValue(severity) : undefined
      const input: RemediationInput = {
        type: RemediationTypeValues.Mitigation,
        vulnerability,
        service,
        image,
        description: descriptionTrimmed,
        ...(remediatedBy && { remediatedBy }),
        ...(severityValue !== undefined && { severity: severityValue }),
        expirationDate: expirationDate.toISOString(),
      }

[ArtieReus]

The only concern I would have is that the RemediationModal which other actions depends on isn't being tested... What do you think?

[ArtieReus]

great job! thanks for adding tests!

[taymoor89]

[Optional] I think we can reduce number of useStates by grouping related fields like

const [form, setForm] = useState({
  description: "",
  manualUserId: "",
  sourceTicket: "",
  expirationDate: null as Date | null,
})

const [errors, setErrors] = useState({
  description: "",
  userId: "",
  sourceTicket: "",
  expirationDate: "",
})