feat: integrate submit_windowed_post with pallet proofs

[th7nder]

Description

Fixes #449.

1. It implements the logic in submit_windowed_post of Pallet Storage Provider, so it calls Pallet Proofs to verify PoSt.
2. Exposes Runtime API to fetch the current deadline, so current_deadline.challenge will be able to be called in the pipeline Submit Windowed PoSt in the Pipeline #596.

I tested it by running:

1. examples/rpc_publish.sh examples/test-data-big.car
2. export CACHE=<directory outputed in rpc_publish>
3. export COMMR=<commr outputed by rpc publish>
4. export CHALLENGE_BLOCK=<runtime api query call for current_deadline>
5. ./target/release/polka-storage-provider-client proofs post --sr25519-key "//Charlie" --cache-directory $CACHE --proof-parameters-path 2KiB.post.params --sector-number 1 $CACHE/../sealed/1 --challenge_block $CHALLENGE_BLOCK $COMMR
6. submit_windowed_post via polkadot.js.org with the file 1.sector.proof.post.scale.

+

CACHE_FOLDER="/tmp/F8JAt9d/deals_storage/cache"

PROVIDER="//Charlie"
CAR_FILE="../examples/test-data-big.car"
SECTOR_ID=1

COMMR="bagboea4b5abcauws63b3gksuxld4zxk7jlzx776kmh66rokcngcvhtwsuksxpklm"
CHALLENGE_BLOCK="108"
POST_PARAMS_PATH="../2KiB.post.params"

polka-storage-provider-client proofs post \
--sr25519-key "$PROVIDER" \
--proof-parameters-path "$POST_PARAMS_PATH" \
--cache-directory "$CACHE_FOLDER" \
--sector-number "$SECTOR_ID" \
--challenge-block "$CHALLENGE_BLOCK" \
"$CACHE_FOLDER/../sealed/$SECTOR_ID" \
"$COMMR"

Important things

• maat test is broken! I need to fix it, but it's out of the scope as I'm planning bigger changes to it.

Checklist

• Make sure that you described what this change does.
• If there are follow-ups, have you created issues for them?
  • If yes, which ones? / List them here
    • feat: handle recovered and declares faults in Windowed PoSt #592
    • Add support for multiple partitions when verifying PoSt #595
    • Submit Windowed PoSt in the Pipeline #596
    • fix(maat): refactor it so it uses pipeline as a library #615
• Have you tested this solution?
• Were there any alternative implementations considered?
• Did you document new (or modified) APIs?

[cernicc]

Good job 💪