MTG-1057 Add consistency check tools

[n00m4d]

What

This PR adds new package with two binaries: compressed_assets and regular_assets. That two binaries are verifying if our RocksDB is consistent.

How

Compressed assets

This binary takes a csv file with cNFT tree addresses and verifying if each minted asset in a tree has valid proofs.

Regular assets

This binary takes solana accounts snapshot, iterates over it and checks if RocksDB contains all the NFTs and token accounts.

[StanChe]

Mostly spelling, several comments on args types and some improvements suggested. It'll work as it is, so either create additional tickets and merge or fix some comments and put non done into tickets

[StanChe]

Why not the version from the workspace? Same question applies to other versions below

[StanChe]

Suggested change

	Binary `compressed_assets` is taking `csv` file with tree keys and check proof for each minted asset in a tree.
	The binary `compressed_assets` takes a `csv` file with tree keys and checks the proof for each minted asset in a tree.

[StanChe]

Suggested change

	Here is example of `csv` file it expects to receive:
	Here is an example of the `csv` file it expects to receive:

[StanChe]

Suggested change

	Workers parameter points how many trees will be processed in parallel.
	The `workers` parameter points to how many trees will be processed in parallel.

[StanChe]

Suggested change

	Inner workers parameter points how many threads each worker will use to process the tree.
	The `inner-workers` parameter points to how many threads each worker will use to process the tree.

[StanChe]

Suggested change

	db_path: String,
	db_path: PathBuf,

[StanChe]

Suggested change

	trees_file_path: String,
	trees_file_path: PathBuf,

[StanChe]

The method is fixed and will return proofs for a list of assets. I'd suggest we pass in at least a 1000 assets, but in theory a whole chunk will be possible (although memory intensive)

[StanChe]

Should be an arg with PathBuf type and this value as default

[StanChe]

This may produce false positives. We already have the method

  pub(crate) fn sync_has_key(db: Arc<DB>, key: C::KeyType) -> crate::Result<bool> {
        let cf = &db.cf_handle(C::NAME).unwrap();
        let encoded_key = C::encode_key(key);
        if !db.key_may_exist_cf(cf, &encoded_key) {
            return Ok(false);
        }
        let res = db.get_cf(cf, &encoded_key)?;
        Ok(res.is_some())
    }

I'd suggest wrapping it with async instead

[StanChe]

this looks like a mix of some custom code and some code copied from Solana. If anything changes on their end, it'll be tricky to support the changes. I presume we couldn't reuse the types from Solana, could we? If we couldn't I'd suggest putting all the copied code in a separate file/files with minimal to no changes and adding custom logic beside it.