Additional curation target types

[dblodorn]

Would be interesting to support (or explicitly type) curation of

• transaction hashes: imagine it would be quite interesting to view a collection of novel transactions (fund transfers) deploys, etc. 🤷‍♂️
• Block number... again not exactly sure why, but this seems to be an interesting data point that could be collated in compelling ways.

https://github.com/public-assembly/curation-protocol/blob/main/src/interfaces/ICurator.sol#L8-L21

[0xTranqui]

so I think this would be really cool and totally represent meaningful blockchain data to curate, however there is an issue with adding this functionality for a few reasons:

1. see screenshot below for what information is stored in the listing struct. as of now, all Curation Types have an address component (line 26 of ICurator.sol). as listings allow u to curate bytes data (transaction hashes) or uints (block numbers), we would need to allow for the curation of other solidity data types, which would require foundational changes into how data is stored.

2. this could potentially be addressed by extracting curation types + listing structs out of the curation protoocl and into external onchain registries (like we did for access control), but that is a significant rewrite of the current architecture

am very open to this, but initial thinking at solution would require something pretty significant