Improve UX when a World is blocked for exceeding storage limits

## Description

When a World exceeds its allowed storage quota, it gets blocked and becomes inaccessible — but creators are given no explanation for why. From the user's perspective, teleporting to the World simply fails silently and they are redirected back to Genesis Plaza, with no error message, warning, or notice anywhere in the client, Builder, or Creator Hub explaining what happened or how to fix it.

This was reported after a creator (Chiri) could not teleport to her World (`Impssbldimnsn.dcl.eth`). She assumed it was a bug, when in fact the World had exceeded its storage allowance.

## How the current flow works (confirmed via code/docs)

- **New deployment** exceeding the *current* quota → hard-rejected at upload time by `worlds-content-server` (`createValidateSize` in `src/logic/validations/scene.ts`, checked against `limitsManager.getMaxAllowedSizeInBytesFor`). This case already fails clearly for the creator.
- **Existing deployed content** exceeding quota *after the fact* (e.g. the creator's wallet holdings shrink because they transfer/sell NAMEs or spend MANA, lowering their storage cap) → per the , there's a 24h grace period before the World becomes inaccessible. This is the scenario that hit the reported user, and it's the one with no in-product warning.

Available storage is only visible if the creator proactively checks the Builder "Worlds" tab or the Creator Hub "Manage" tab — there's no proactive notification when the quota is exceeded or when the grace period starts/ends.

## Problem

1. No message, warning, or popup tells the creator that their World has been blocked due to exceeding storage limits.
2. No indication that a 24h grace period exists, or how much of it is left, before the World becomes inaccessible.
3. When teleporting to a blocked World, the client silently redirects back to Genesis Plaza with no explanation — making it look like a bug rather than an expected consequence of exceeding storage.
4. It's unclear to creators whether they can still deploy to a World while it is in this blocked/grace-period state (in the reported case, the creator was apparently still able to deploy the same day, adding to the confusion about the World's actual status).

## Proposed improvement

- Surface a clear, explicit warning in Builder / Creator Hub when a World's current storage usage exceeds its allowed quota, including remaining grace period time before it becomes inaccessible.
- Consider a proactive notification (email/in-app) when a wallet-holdings change (e.g. transferring a NAME or spending MANA) causes an owned World to cross into the blocked state.
- Investigate/clarify (possibly file separately against the Explorer) why teleporting to a blocked World silently redirects to Genesis Plaza instead of showing an in-client message explaining the World is inaccessible due to exceeded storage.

---
Reported by Dawid Krajewski
Requested by Rocío Corral Mena via Slack