Project waking UI state

[ericokuma]

Fixes APP-626: Persists project waking UI state across navigation

Previously, navigating away from a project during its "waking" process would cause the UI to revert to the hibernation banner, even though the backend process continued. This happened because the wakingProjects state was being reset or not consistently accessed across page loads.

This PR ensures the "waking" UI state is correctly persisted and displayed across different pages within an organization.

• BillingCTAHandler.get no longer resets the wakingProjects state.
• BillingBannerManagerForAdmins and OrganizationHibernatingForAdmins now consistently use a shared, organization-level BillingCTAHandler instance to access the persistent wakingProjects state.
• The BillingBannerManagerForAdmins prioritizes displaying the "Waking projects..." banner when wakingProjects is active, preventing it from being overwritten by the default hibernation message.

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!

---

Linear Issue: APP-626

  

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}