feat: do not show `_SIMONdotBLACK_` spam on `Input Data` field of contract deployment

[zerosnacks]

Describe the solution you'd like

See: https://www.4byte.directory/signatures/?bytes4_signature=0x60806040, this matches with the first 4 bytes of any contract deployment: 0x60806040...

We currently decode this Input Data here:

People do this for free advertising / tagging culture.

I think we should just add some conditional handling for specifically this case given all contract deployments show this for their genesis.

[zerosnacks]

Perhaps there is a general way to avoid this if we are using OpenChain's API: https://4byte.sourcify.dev/?q=0x60806040, they do active flagging of spam hash collisions and maybe they expose that in some way (if not, we can ask them)

[kuzdogan]

Hey it's just a list of canonical signatures :) Feel free to open a PR for your needs

https://github.com/argotorg/sourcify/blob/staging/services/4byte/src/utils/canonical-signatures.json

We thought about filtering more but didn't prioritize this as we didn't receive any feedback regarding spams.

We have a short analysis on this too https://docs.sourcify.dev/blog/signatures-analysis/