fix: incorrect computing price-per-bytes in retrieval client

[zl03jsj]

关联的Issues (Related Issues)

close filecoin-project/venus#4908

改动 (Proposed Changes)

The approach of computing price per byte in retrieval client is incorrect,

the order.Total is the total price to retrieve the piece, its value is size * MinPricePerByte + UnsealedPrice
https://github.com/filecoin-project/go-fil-markets/blob/master/retrievalmarket/types.go#L216

with following approach to compute price per byte:
https://github.com/filecoin-project/venus-market/blob/ab7c180f5a65a1c7ab549cfca78463f2a9329fbc/client/client.go#L803

if order.UnsealPrice is not 0, this causes price per byte(ppb) larger than it's actual amount..
this would finally cause retrieval deal failed with ClientEventVoucherShortfall

following is the Fragment of this issue:

Recv 30.01 MiB, Paid 0.0000001 FIL, VoucherShortfall (CheckFunds), 1m48.883s
Recv 30.01 MiB, Paid 0.0000001 FIL, FundsExpended (InsufficientFunds), 1m49.065s

自查清单 (Checklist)

在你认为本 PR 满足被审阅的标准之前，需要确保 / Before you mark the PR ready for review, please make sure that:

• 符合Venus项目管理规范中关于PR的相关标准 / The PR follows the PR standards set out in the Venus project management guidelines
• 具有清晰明确的commit message / All commits have a clear commit message.
• 包含相关的的测试用例或者不需要新增测试用例 / This PR has tests for new functionality or change in behaviour or not need to add new tests.
• 包含相关的的指南以及文档或者不需要新增文档 / This PR has updated usage guidelines and documentation or not need
• 通过必要的检查项 / All checks are green

[diwufeiwen]

LGTM

[hunjixin]

LGTM