feat: add per-component remediations type to EolScanComponent

[facundo-herodevs]

What This Branch Does

Adds a typed, per-component remediations field to the shared EOL scan model. A new
Remediation
type (plus its supporting union and target/action types) is introduced and exposed on
EolScanComponent
as an optional field. Types-only change with no runtime behavior.

Remediations Type

Mirrors the EnrichedRemediationFact shape served by eol-api so consumers get a precise type instead of untyped passthrough.

• RemediationType — union: nes_available | nes_ready | version_update | package_replacement.
• RemediationActionType — union: direct | contact | enterprise_portal | automated | reference.
• RemediationAction — { type, url? }.
• RemediationTarget — { purl, version?, releasedAt?, publishPurl?, nesPurl?, ossPurl? }.
• Remediation — { type, description, action, target? }.
• EolScanComponent.remediations — new optional Remediation[] | null field, sibling of nesRemediation.

All types are re-exported from the package root via export type * from './types/eol-scan.js'.

Compatibility

Additive and backward-compatible: the new field is optional, so existing consumers and fixtures compile unchanged. No runtime logic changes.

Known Gaps / Downstream

• Consumed by the HeroDevs CLI to include remediations per component in its saved JSON report; the CLI bumps its dependency to the tag cut from this PR (v0.1.20).
• Release coordination: the CLI must not ship until the eol-api prod schema exposes EolComponentScanResult.remediations, or the CLI's GraphQL query selecting remediations fails validation. Depends on the eol-engine prod cutover + API deploy.