Pull sanitize crate out of solana-program

[kevinheavey]

Problem

The Sanitize trait is a de facto internal trait that doesn't belong in solana-program, and it makes it harder to move a bunch of other things out of solana-program

Summary of Changes

Move sanitize.rs into a new solana-sanitize crate.

[buffalojoec]

So, just to summarize, we're introducing a leaf-node crate for solana-santize.

The monorepo packages which need the Sanitize trait are:

• bloom
• core
• gossip
• version

The Sanitize trait itself is designed for sanitizing over-the-wire message payloads, and >90% of downstream user cases of SDK and program SDK, will never need sanitize().

Regardless, here they are listed for posterity:

• blake3 hashing
• hash (sha2) hashing
• keccak hashing
• CompiledInstruction
• Pubkey
• Signature
• Almost all transaction message types
• Almost all transaction types

I'm in favor of this change. I think it makes sense for networking-related libraries to import solana-sanitize if they need to rely on sanitized messages, and not to impose this requirement on other users of SDK types.

[buffalojoec]

Lgtm @kevinheavey, thanks for the continued crusade on dependencies!

On crates.io, add anza-team and pull yourself as owner, and then retry the CI job.

[kevinheavey]

Added, will remove myself as owner once anza-team accepts the ownership invite https://crates.io/crates/solana-sanitize/

[buffalojoec]

Looks good, just change the deprecated "since" version.

[buffalojoec]

Lgtm, thanks!

[mergify]

automerge label removed due to a CI failure