bug(ui): Create Purchase Plan button does nothing when Azure provider filter is active

[rocketri]

Summary

On the Recommendations tab, when the Provider filter is set to Azure, clicking Create Purchase Plan opens no modal and produces no visible response. The button fires its click handler but nothing happens.

Steps to Reproduce

1. Navigate to the Recommendations tab
2. Set the Provider filter to Azure
3. Click Create Purchase Plan
4. Observe: no modal appears, no error shown

Expected Behaviour

Clicking Create Purchase Plan should open either the recommendation selection modal or the plan creation modal, pre-populated with the active Azure filter context.

Notes

The button works correctly when no provider filter is applied. The failure appears specific to the Azure-filtered state. No console errors were observed — the handler likely returns early on an empty selection without surfacing feedback to the user.

🤖 Found via Playwright Azure UX test

[rocketri]

AWS confirmation (2026-04-24): Reproduced with AWS provider filter active. Clicking 'Create Purchase Plan' while recommendations are filtered to AWS did not open any modal (neither #select-recommendations-modal nor #plan-modal became visible). The button is unresponsive under any provider filter, confirming this is not Azure-specific.

[cristim]

Fixed and merged in PR #35 (commit 0ff59e49d).

Change

openCreatePlanModal no longer early-returns behind a warning toast when the selection is empty. The modal always opens; the title switches dynamically:

• Create Purchase Plan when at least one recommendation is selected
• New Purchase Plan when selection is empty (Azure-filter-with-no-ticks case, or post-filter-switch stale selection)

Same flow as the dedicated 'New Plan' button elsewhere in the UI. Never silently no-ops.

Verification on AWS Lambda deploy

• Deployed js/app.3314f9ad.js contains the new 'New Purchase Plan' fallback title.
• Deployed bundle has 0 occurrences of the old 'Please select at least one recommendation' string.

GCP Cloud Run deploy also green for this commit (migration issue that failed PR #31's deploy has cleared). Azure Container Apps was still in progress at comment time.