Overlapping simultaneous SITES deployments leaves Core region in a bad state but not other regions / edges

### 👟 Reproduction steps 1. Deploy a NextJS Site with images via GitHub push 2. While it is still deploying push another update from Github 3. Go to Console and cancel the first deployment while both are still deploying 4. Wait for 2nd deployment to finish and activate if not activated. 5. Use VPN to test the site from different regions. NYC was the Core region in my test. <img width="831" height="543" alt="Image" src="https://github.com/user-attachments/assets/545ae7aa-97c2-488c-b1c6-cc36c4ddc557" /> ### 👍 Expected behavior Site should load properly with images from all VPN regions. Deployments should be identical in all regions / edges. ### 👎 Actual Behavior Only the index.html (and maybe styling, and some of the images) loads or a Timeout (runtime_timeout) occurs in the Core (deployment) region. Other regions are less affected. Theory - Cancelling the first deployment leaves that deployment in a bad state. The second deployment finishes and marks the bad state deployment as the final completed deployment for the Core region. The good deployment is copied to the other regions. Only the Core region is affected by the cancelled deployment. ### 🎲 Appwrite version Appwrite Cloud ### 💻 Operating system MacOS ### 🧱 Your Environment Windows 11 (Opera browser), MacOS (Safari, Chrome) from Toronto, Canada. ### 👀 Have you spent some time to check if this issue has been raised before? - [x] I checked and didn't find similar issue ### 🏢 Have you read the Code of Conduct? - [x] I have read the [Code of Conduct](https://github.com/appwrite/.github/blob/main/CODE_OF_CONDUCT.md)