Manually Import Data Not Able to Add Piece

### 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 or enhancement request. If it is, please open a [new idea discussion](https://github.com/filecoin-project/boost/discussions/new?category=ideas) instead. New feature and enhancement requests would be entertained by the boost team after a thorough discussion only.
- [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.
- [X] 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
- [ ] Other

### Boost Version

```text
boost version 1.5.1-rc2+git.2c5604e
boostd version 1.5.1-rc2+git.2c5604e
```

### Describe the Bug

After successful manually import-data, boost showed the deal was published and add piece was called. However, lotus-miner displayed error of the add piece action and boost was not aware and still waiting.

expected behavior
1). miner successfully start the sealing process including add piece, pc1, and others
2). boost is aware of the sealing progress, either success or failure.

### Logging Information

```text
Here is the boost log:

2022-12-03T09:59:03.984-0800 INFO boost-storage-deal logs/log.go:40 size of imported offline deal file {"id": "1049f1be-8810-4dec-bdc3-a5be9e3d9238", "filepath": "/media/data/deals/spade/baga6e~cvfq2cki.car", "size": 18263578306}
2022-12-03T09:59:03.985-0800 INFO boost-storage-deal logs/log.go:40 deal execution in progress {"id": "1049f1be-8810-4dec-bdc3-a5be9e3d9238"}
2022-12-03T09:59:03.986-0800 INFO boost-storage-deal logs/log.go:40 deal has already been published and confirmed-publish {"id": "1049f1be-8810-4dec-bdc3-a5be9e3d9238"}
2022-12-03T09:59:03.987-0800 DEBUG boostd boostd/run.go:105 Getting API endpoint of boost node
2022-12-03T09:59:03.987-0800 INFO boost-storage-deal logs/log.go:40 funds successfully untagged for deal after publish {"id": "1049f1be-8810-4dec-bdc3-a5be9e3d9238"}
2022-12-03T09:59:03.987-0800 INFO boostd boostd/run.go:118 Boost libp2p node listening {"maddr": "{12D3KooWRkyFskoWEr7wGG6rSm8bCaNVY4cvfMogsLtbPt8P3sYD: [/ip4/66.114.139.188/tcp/63452]}"}
2022-12-03T09:59:03.988-0800 DEBUG boostd boostd/run.go:126 Bootstrapping boost libp2p network with full node {"maadr": "{12D3KooWH6oF23EM19i9GzWFCJbUKEREVaqJ2yhtvLUNa7HM9F5v: [/ip4/10.1.18.169/tcp/46543 /ip4/127.0.0.1/tcp/46543 /ip6/::1/tcp/35149 /ip4/66.114.139.188/tcp/46543]}"}
2022-12-03T09:59:03.990-0800 INFO boost-storage-deal logs/log.go:40 add piece called {"id": "1049f1be-8810-4dec-bdc3-a5be9e3d9238"}

Here is the miner log:

2022-12-03T10:06:18.770-0800 WARN rpc go-jsonrpc@v0.1.8/handler.go:329 error in RPC call to 'Filecoin.SectorAddPieceToAny': context canceled
2022-12-03T10:06:18.949-0800 ERROR rpcenc rpcenc/reader.go:408 context error in reader stream handler (2): context canceled
2022-12-03T10:06:34.108-0800 INFO sectors pipeline/input.go:286 Adding piece for deal 17736717 (publish msg: bafy2bzacedbdvf5vcncdjnijunvmwvmlnfkanmd4shbvyfllosnle4gjygnki)
```

### Repo Steps

1. Run manual deal import to boost using boostd import-data
2. Check boost to make sure the import was successful
3. Wait for boost to publish the deal message
4. Boost started a call to miner API to start sealing process with Add Piece
5. Miner errored with add piece context cancelled

Start by reproducing the manual import with `boostd import-data`, then trace the add-piece call after the deal is published. Compare the Boost storage-deal logs with the miner RPC errors for `SectorAddPieceToAny` and the subsequent sealing-pipeline message. Done means Boost detects and reports whether the miner’s add-piece and sealing process succeeds or fails.

Written by the indexing model from the issue text.