feat: use hash based record verification for chunks

[RolandSherwin]

Description

Summary generated by Reviewpad on 07 Dec 23 15:52 UTC

This pull request includes changes to multiple files.

• The mod.rs file in the messages module adds support for chunk proofs and organizes message-related components.
• Changes in the FilesCmds enum, upload_files and upload_chunk functions remove the show_holders functionality.
• The QueryResponse enum adds new variants for GetStoreCost and GetChunkExistenceProof queries.
• The Node implementation in the node.rs file adds support for handling GetChunkExistenceProof queries.
• The Cargo.toml file adds the tiny-keccak dependency.
• Changes in the query.rs file update imports and add new variants to the Query enum.
• The chunk_proof.rs file adds the ChunkProof struct and associated methods.
• Changes in the Files implementation simplify parameter passing and remove unused show_holders functionality.
• Changes in various files import ChunkProof and modify functionality related to chunk storage and verification.
• Changes in the event.rs file modify the SwarmDriver implementation for handling Kademlia events.
• Changes in the error.rs file import types and add new error variants for chunk existence and register not found.
• Changes in the file add new functions for retrieving chunk proofs and store costs from the network.

Please review these changes and let me know if you have any questions.

[joshuef]

added DoNotMerge as breaking change we may not want in juusst yet

[reviewpad]

Reviewpad Report

‼️ Errors

• Unconventional commit detected: 'chore(cli)!: remove show_holders flag as we perform that by default

• during hash based verification' (365f9f4)

[maqi]

by making ChunkProof constructor taking a chunk_name instead of whole content will be enough,
and has the benefit of avoid un-necessary access to the whole content?
especialy at the previous place of

                    // make sure the chunk is stored;
                    let chunk = Chunk::new(Bytes::from(std::fs::read(&chunk_path)?));
                    let res = client.verify_chunk_stored(&chunk).await;

which has to read from disk ?

[RolandSherwin]

This can lead to dishonest nodes just storing the keys and discarding the content. And the proof that they create would be valid.

[maqi]

ah, right, make sense.