monorepo: revert and adjust some prefixedHexTypes

[gabrocheleau]

This PR reverts some updates that had been made to string in #3348 and #3357, where string types were updated to PrefixedHexString when that was relevant, but this can lead to breaking changes in certain contexts. I've reverted what seemed like the most obvious common usages (e.g. block or common types that can be used externally). Instead of actually reverting to string, I updated the types to PrefixedHexString | string so that we can easily eventually remove string fully. I've also added TODO's above each of these instances so we can quickly retieve these instances and do that eventually.

[acolytec3]

LGTM

[holgerd77]

Cool 🎉, can you also add a note to #3216 ?

[holgerd77]

Oh. This seems wrong I guess?

[holgerd77]

I could instantly spot too missed instances, hexToBytes() and intToHex() which are still missed, so I think we need to do a closer search here what is still missing.

(or are these not breaking for some reasons?)

[gabrocheleau]

I could instantly spot too missed instances, hexToBytes() and intToHex() which are still missed, so I think we need to do a closer search here what is still missing.

(or are these not breaking for some reasons?)

Circling back to this.

I don't think that methods that output PrefixedHexString are a problem (since PrefixedHexstring can be assigned to string, it shouldn't break anything). However taking PrefixedHexString as input is definitely breaking. I can revert hexToBytes. We'll have the best of both worlds in a way, as we have already updated all the monorepo. We can perhaps consider then re-switching to PrefixedHexString only in a future release.

[gabrocheleau]

Addressed in #3427 @holgerd77