explode common

[pro-wh]

this is a draft to see what it would be like.

separate them to have their own prefixes/modules based on the Go codebase's detailed breakdown of the 'common' directory.
I kinda don't like it. but it may be more sustainable if we end up having types with the same name in different 'common' subpackages.

also tries out removing duplicate parts of names, e.g. CommonNode -> NodeNode -> Node.
I kinda don't like that either. seems like we had done this in the Go codebase with things like consensus.Parameters instead of consensus.ConsensusParameters. we had a lint for it, formerly known as 'stutter' rust-lang/rust-clippy#3521. I personally would have preferred rule simplicity and consistency across packages and longer name (consensus.ConsensusParameters) over the lint rule's more complex rule, less consistency across packages, and shorter name (consensus.Parameters). viva HTMLHtmlElement too

oh and this causes us to have a cbor module while our actual cbor helpers are in misc. hm

[pro-wh]

let's go ahead with the type name changes, but not the module changes.