fix: Support for BMFF V3 hashing options (#1253)

* Support for BMFF Hash V3
validation of fixedBlockSize and fixedBlockSizes Merkle trees
generation of fixedBlockSize Merkle trees

* Bug fix for case when BMFF exclusion subset is using length with no offset

* Setting to control Merkle tree storage

* Change error message

* More error checking
PR comment change

* Make settings fetch return error is not set

* Add test for no fixed offset

* Fix formatting

* Check for conflicting block types

* Fix error response for competing Merkle block types

* Make spec responses

* Allow 0 length fixed offset

* A little cleanup

* Make sure there is a recognized hash binding

* Fix for some more edge cases

* clippy fix

---------

Co-authored-by: Gavin  Peacock <[email protected]>

Author: mauricefisher64

sdk/examples/data_hash.rs

@@ -118,7 +118,7 @@ fn user_data_hash_with_sdk_hashing() -> Result<()> {
 
     // we need to add a data hash that excludes the manifest
     let mut dh = DataHash::new("my_manifest", "sha265");
-    let hr = HashRange::new(manifest_pos, placeholder_manifest.len());
+    let hr = HashRange::new(manifest_pos as u64, placeholder_manifest.len() as u64);
     dh.add_exclusion(hr.clone());
 
     // Hash the bytes excluding the manifest we inserted
@@ -176,7 +176,7 @@ fn user_data_hash_with_user_hashing() -> Result<()> {
     // Figure out where you want to put the manifest, let's put it at the beginning of the JPEG as first segment
     // we will need to add a data hash that excludes the manifest
     let mut dh = DataHash::new("my_manifest", "sha265");
-    let hr = HashRange::new(2, placeholder_manifest.len());
+    let hr = HashRange::new(2, placeholder_manifest.len() as u64);
     dh.add_exclusion(hr);
 
     // since the only thing we are excluding in this example is the manifest we can just hash all the bytes