Store and return contract hashes

[whoabuddy]

We create a sha256 hash of the source code for all DAO contracts.

We should create a durable object that let's us store this information and retrieve it.

• in any of the deploy- scripts we can add a method to submit the hash
• in the cache we can verify the hash against taking the hash of the contract source from the API
• in the frontend we can use it to display "verified" contracts. (h/t Louis for the idea!)
• in other UIs/integrations we can encourage the same - they can either hash it from source or get our list of hashes
• goal: entire list can be rebuilt from data on-chain

[whoabuddy]

After reviewing DO design I think we can close this out - in the future if we want to revisit, it'd be better to:

• create a DO per contract principal
• use that DO to store transactions, contract code, contract hash, etc in a consistent format
• scale queries across which contract is being interacted with
• (or something like that)

ALTHOUGH a KV cache that returns the hash is interesting because it'd be blazing fast...