feat(readiness): Add shared AWS program library to portfolio TDs

[lusoal]

Introduce a shared AWS Program & GTM Library as a reference file and wire it into the two portfolio readiness Task Definitions so the analysis agent can recommend relevant AWS programs in the "Next Steps" section of reports.

• Add readiness-analysis/references/program-library.md: 88 programs (35 Tier 1 detailed incl. 3 ARA agentic anchors, 53 Tier 2 compact) with signal patterns, qualification criteria, prioritization, grouping, and status filtering. Aligns trigger vocabulary to actual ARA/MOD findings.
• Wire portfolio ARA Step 7 and portfolio MOD Step 9 to load the library; replace inline program catalogs with library references.
• Move AI DLC, AXE, and Innovation EBA out of the portfolio ARA TD into the library as ARA anchor programs.
• Group recommendations Funded -> Engagement -> GTM, cap at 3-5, and never expose the internal MOD 1-4 score.
• Update both portfolio HTML visual contracts to render the full grouped library set with a Group column.
• Add per-repo ARA/MOD pointer notes clarifying program recommendations are portfolio-level only; remove hardcoded program names from the per-repo ARA HTML contract.
• Fix stale portfolio TD filenames in the README directory tree and table

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[aritnag123]

Tested the updated portfolio MOD TD from PR #54. Programs are showing up correctly ✅

Setup:

• Pushed the portfolio-mod TD + program-library.md (as document_references/) to my personal registry
• Ran 2 per-repo MOD analyses (PHP monolith fixture + books-api), then the portfolio TD

Results:

• 4 programs recommended from the library, grouped correctly:
    - Funded: AppMod Assessment, SHIP
    - Engagement: Immersion Days
    - GTM: Agentic-led Modernization Sales Play
• Each recommended_actions[] entry has group field ✅
• Capped within 3-5 range ✅
• No internal MOD 1-4 scores exposed ✅
• Per-repo reports clean (no program names, just pointer to portfolio TD) ✅

Notes for others testing:

• The TD file must be named transformation_definition.md, references go in document_references/ (not references/)
• Portfolio TDs require minimum 2 per-repo reports or they'll fail with entry criteria error
• Use -x -t flags for non-interactive execution

LGTM from my side 👍