[QA] Backpack | Stuck, unclosable error toast during wearable equip failure

### 🛠️ **Build version:**
v0.156.0-alpha-fix/chat-enter-focus-stacked-popups-da11959

### 📔 **Issue Description:**
While smoke testing wearables, an error toast ("There was an error loading your avatar wardrobe. Please try again.") appeared and got stuck — greyed out and not fully clickable, unable to be dismissed. Player.log shows a genuine backend rejection during this window: `BackpackEquipStatusController.UpdateProfileAsync` threw `UnityWebRequestException: HTTP/1.1 400 Bad Request {"errors":["There was an error deploying the entity"]}`, occurring twice in quick succession shortly before a scene reload.

### 👣 **STR:**
1. Open Backpack / wearables while connected
2. Rapidly switch/equip wearables (change too fast for the server to keep up)
3. Observe the error toast when the equip/profile deploy is rejected

### ✔️ **Expected Result:**
Error toast should be dismissible (clickable "x" or auto-clear), and equip failure should not leave a persistent, unclosable UI element.

### ❌ **Actual Result with evidence:**
Toast remains on screen, greyed out, and cannot be closed. Player.log confirms a real HTTP 400 profile deploy failure at the time the toast appeared (not a false positive or noise error).

### ➗ **Reproduction:**
##### ⚠️ Intermittent - (seen twice in one session log, tied to rapid wearable changes; not yet confirmed as 100% reproducible on demand)

#### 🖥️ **Operative system and additional Notes:**
macOS, Apple M3 Pro. Note: `WEARABLE`, `BACKPACK`, and `UI` log categories are suppressed in this alpha build, so no further diagnostic detail is available beyond the exception trace itself.

Discovered while testing https://github.com/decentraland/unity-explorer/pull/9367 but this issue doesn't seem related to this PR. I wasn't able to repro on Prod, but will monitor and update this comment in case I do.

https://github.com/user-attachments/assets/364893ff-b54a-457d-a945-0084b732e69e

[Player 9367.log](https://github.com/user-attachments/files/30042320/Player.9367.log)