Issue:
[BUG] Docker compose failing because of the web module not having healthcheck

### Bug Description

When `docker compose up -d` is ran, it returns the following error message:
`dependency failed to start: container hyperswitch-hyperswitch-web-1 has no healthcheck configured`

### Expected Behavior

The Web module should be started

### Actual Behavior

The Web module doesn't start due to this

### Steps To Reproduce

1. Clone repo from scratch
2. Run `docker compose up -d`

### Context For The Bug

This can be resolved with either adding a healthcheck part to the web module or changing the demo part to not require healthcheck from the web part. Additionally, we could only check if it has started rather than if it is healthy, as that is something which works.

### Environment

I am running this locally.

1. Operating System or Linux distribution: Mac OS X 15.4 M3 Pro
2. Rust version (output of `rustc --version`): /
3. App version (output of `cargo r --features vergen -- --version`): /


### Have you spent some time checking if this bug has been raised before?

- [x] I checked and didn't find a similar issue

### Have you read the Contributing Guidelines?

- [x] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

No, but I'm happy to collaborate on a PR with someone else

Resolution:
<think>
PR Context:
- Title: fix: fixes the docker setup to clean up the scarf data
- Merged: 2025-05-12T08:26:50Z
- Files changed: 2 files
- Commits: 3 commits

Implementation approach:
## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [X] Bugfix
- [ ] New feature
- [ ] Enhancement
- [ ] Refactoring
- [ ] Dependency updates
- [ ] Documentation
- [ ] CI/CD

## Description
<!-- Describe your changes in detail -->
The hyperswitch server would run even without the completion of migration runner polluting the data in the scarf dashboard.

### Additional Changes

- [ ] This PR modifies the API contract
- [ ] This PR modifies the database schema
- [ ]
</think>

To implement this, you'll need to modify:


(No detailed commit information available)