fix: add error response from wake project CTA

[AdityaHegde]

There is on reliable way to reproduce this. The original issue probable hit some edge case while processing billing issues.

Closes ENG-1007

Checklist:

• Covered by tests
• Ran it and it works as intended
• Reviewed the diff before requesting a review
• Checked for unhandled edge cases
• Linked the issues it closes
• Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
• Intend to cherry-pick into the release branch
• I'm proud of this work!

[ericpgreen2]

Feedback: Retry path on error

The error state shows a banner with no action — if this fails, how does the user retry?

Currently, they'd need to navigate to the org page where the inline "Wake projects" button lives (OrganizationHibernatingForAdmins.svelte). That works, but it's not obvious from the error banner.

Quick fix options:

1. Add a "Retry" button CTA to the error banner (the banner system supports type: "button" with an onClick callback)
2. Add a "Go to projects" link so users know where to retry

Longer-term observation: The org page already has a nice inline flow for this (loading state, button, etc.). The banner-based wake flow duplicates that logic in a less ideal place — banners aren't great for loading states or multi-step interactions. A cleaner design might be: banner just links to the org page, org page handles the actual wake action. That's a larger change though, so not suggesting it for this PR unless you want to take it on.

---

Developed in collaboration with Claude Code

[AdityaHegde]

Note that wake up banner is an edge case. The main use case is to show billing related messages. These are meant to be shown across pages, so it makes sense for them to be banners.

We already have full page wake projects message. We had decided to duplicate it in banners as well.