feat(model-lifecycle): monitor Bedrock model lifecycle status, alert on change

[timmanik]

Summary

• New weekly monitor (ModelLifecycleMonitor construct + abe-model-lifecycle-monitor Lambda) that checks modelLifecycle.status for every Bedrock model in config.yaml, since AWS Health's deprecation notices require a support plan we don't have.
• Diffs against a last-seen status map in SSM (/abe/model-lifecycle/last-status); the first run just establishes the baseline (no email), later runs email one alert per model whose status changed, explaining what LEGACY/EOL/ACTIVE mean and AWS's 6-month minimum LEGACY lead time.
• Inference-profile ARNs are resolved to their underlying foundation-model ARN via GetInferenceProfile before calling GetFoundationModel (which rejects inference-profile ARNs directly), picking the region-qualified ARN rather than the region-less one GetInferenceProfile also returns.
• Notification recipients come from a new model_lifecycle_notification_email config key, kept separate from notification_email so this doesn't fire SNS confirmation emails at the existing content-sync list.
• Weekly schedule: Mondays 8am ET (same slot as the conversation export - separate Lambda/schedule, no conflict).

Test plan

• cdk synth / cdk diff reviewed - only the new topic/subscription/Lambda/IAM/schedule resources added
• Deployed to the dev account; SNS subscription confirmed
• First invoke established the SSM baseline silently (no email)
• Forced a fake prior status in SSM, re-invoked - alert email fired and SSM self-healed to the real current status afterward
• Verified the region-ARN fix resolves GetFoundationModel correctly for the inference-profile-backed models
• Reviewed final email wording for both directions (LEGACY and back to ACTIVE)