Log spam: indexprovider/wrapper.go:159 -> "seal status Removed"

### Checklist

- [X] This is **not** a question or a support request. If you have any boost related questions, please ask in the [discussion forum](https://github.com/filecoin-project/boost/discussions).
- [X] This is **not** a new feature request. If it is, please file a [feature request](https://github.com/filecoin-project/boost/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Ffeature&template=feature_request.yml) instead.
- [X] This is **not** an enhancement request. If it is, please file a [improvement suggestion](https://github.com/filecoin-project/boost/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Fenhancement&template=enhancement.yml) instead.
- [X] I **have** searched on the [issue tracker](https://github.com/filecoin-project/boost/issues) and the [discussion forum](https://github.com/filecoin-project/boost/discussions), and there is no existing related issue or discussion.
- [X] I am running the [`Latest release`](https://github.com/filecoin-project/boost/releases), or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
- [ ] I did not make any code changes to boost.

### Boost component

- [X] boost daemon - storage providers
- [ ] boost client
- [ ] boost UI
- [ ] boost data-transfer
- [ ] boost index-provider
- [X] Other

### Boost Version

```text
2.0.0
```

### Describe the Bug

While running the daemon, I keep getting a lot of logs from deals / sectors that have been removed.

This also happened in 1.7.3 and I think it also happened before that.

### Logging Information

```text
{"level":"debug","ts":"2023-10-09T12:01:25.117Z","logger":"index-provider-wrapper","caller":"indexprovider/wrapper.go:159","msg":"sector { 10262} has 0 deals, seal status Removed"}
{"level":"debug","ts":"2023-10-09T12:01:25.658Z","logger":"index-provider-wrapper","caller":"indexprovider/wrapper.go:159","msg":"sector { 24522} has 0 deals, seal status Removed"}
{"level":"debug","ts":"2023-10-09T12:01:26.182Z","logger":"index-provider-wrapper","caller":"indexprovider/wrapper.go:159","msg":"sector { 6824} has 0 deals, seal status Removed"}
{"level":"debug","ts":"2023-10-09T12:01:26.723Z","logger":"index-provider-wrapper","caller":"indexprovider/wrapper.go:159","msg":"sector { 4378} has 0 deals, seal status Removed"}
{"level":"debug","ts":"2023-10-09T12:01:27.236Z","logger":"index-provider-wrapper","caller":"indexprovider/wrapper.go:159","msg":"sector { 10564} has 0 deals, seal status Removed"}
{"level":"debug","ts":"2023-10-09T12:01:27.749Z","logger":"index-provider-wrapper","caller":"indexprovider/wrapper.go:159","msg":"sector { 4523} has 0 deals, seal status Removed"}
```

### Repo Steps

1. Run boost
2. Check logs

Start at indexprovider/wrapper.go:159 and run Boost while checking the daemon logs to reproduce the repeated messages for removed sectors. Trace why sectors with zero deals are logged and verify that the excessive "seal status Removed" output is no longer produced, using the existing logging behavior as the completion check.

Written by the indexing model from the issue text.