Sentry Unstable and not being started

### Self-Hosted Version

26.4.2

### CPU Architecture

x86_64

### Docker Version

29.4.3

### Docker Compose Version

5.1.3

### Machine Specification

- [x] My system meets the minimum system requirements of Sentry

### Installation Type

Upgrade of Monthly Updated Instance

### Steps to Reproduce

1. Setup Sentry in 2022 / 2023
2. Update Sentry every month

### Expected Result

Sentry should startup easy and fast.

### Actual Result

Sentry does not startup at all often and does crash if it started

dependency failed to start: container sentry-self-hosted-seaweedfs-1 is unhealthy
or
dependency failed to start: container sentry-self-hosted-web-1 is unhealthy

This was an issue since many Updates ago but was always thought on the low Hardware-Specs.
But now i upgraded the VM to check for the issue
4 -> 8 Cores
20 GB -> 56 GB RAM
and its still the same issue.
The CPU Load is high (50+) but the RAM and CPU Usage in percent is still low (every core under 50%).
iostat seems fine.

In the past just waiting 30 Mins and running docker compose up -d again worked. But this does not work anymore.

Here the Full log:
https://i.dev4life.de/raw/d844259b-a778-442f-9bf4-28158395d0cc.txt?download=true

Needed to upload to a Server because its to big for Github or its just buggy.

### Event ID

_No response_

Start with the linked full log and the reported failures for sentry-self-hosted-seaweedfs-1 and sentry-self-hosted-web-1. Reproduce the upgrade startup path with docker compose up -d, then use the container health failures and logs to narrow the cause. Done means the upgraded instance starts reliably without unhealthy dependency errors or repeated crashes.

Written by the indexing model from the issue text.