Add support to visually represent addresses and hashes with 'blo'

[Archethect]

As requested in #14, this PR leverages the same library for representing EVM addresses as used in the Safe UI.

I also added support to visually represent the hashes in the same way. Feel free to tell me if you'd like to have this removed if you don't like it @josepchetrit12, @xaler5

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Archethect]

I confirm that I have read and hereby agree to the OpenZeppelin Contributor License Agreement

[josepchetrit12]

Great! Awesome work! Since Safe doesn't use this pixel for hashes, I'd prefer to remove it. Besides, in theory, this library was created for addresses.

I thought maybe there could be a collision, but I tested it and it didn't:

const address = "0x111CEEee040739fD91D29C34C33E6B3E112F2177"
const hash32 = "0x000000000000000000111CEEee040739fD91D29C34C33E6B3E112F2177"

I think I'd also reduce the size of the pixel

[josepchetrit12]

Maybe we also want to round the corners like in safe, what do you think?

[Archethect]

Great! Awesome work! Since Safe doesn't use this pixel for hashes, I'd prefer to remove it. Besides, in theory, this library was created for addresses.

I thought maybe there could be a collision, but I tested it and it didn't:

const address = "0x111CEEee040739fD91D29C34C33E6B3E112F2177"
const hash32 = "0x000000000000000000111CEEee040739fD91D29C34C33E6B3E112F2177"

Gotcha. I also checked this, and it just expects any string starting with '0x', therefore both hashes and addresses work.
I'll remove it for hashes.

Maybe we also want to round the corners like in safe, what do you think?

Yes, certainly doable! Regarding the size, let's see what is still visible.

[Archethect]

ok @josepchetrit12 ,

Tell me what you like:

30 px:

25 px:

20 px:

[josepchetrit12]

20px it's the way to go, network image and pixel avatar should be the same size and style!

[Archethect]

ok cool! Change is committed.

[josepchetrit12]

LGTM! Amazing thanks for your contribution!

[ferrabled]

LGTM! Thanks for the changes. Just one small note: there are conflicts in package-lock.json with the main branch (a dependency that it is not being used). We should regenerate the lock file to clean up any unused dependencies to maintain the dependency tree clean and consistent.

[josepchetrit12]

LGTM!

[josepchetrit12]

@Archethect Can you sign your commits? so we can merge this PR! thanks

[Archethect]

@Archethect Can you sign your commits? so we can merge this PR! thanks

Verified/Signed my last noop commit.
Let me know if this is good to go, or you need me to sign all my previous commits as well.
I think if I do that, all other commits will need new signatures because of the rebase though.

[josepchetrit12]

@Archethect Can you sign your commits? so we can merge this PR! thanks

Verified/Signed my last noop commit. Let me know if this is good to go, or you need me to sign all my previous commits as well. I think if I do that, all other commits will need new signatures because of the rebase though.

We need all the commits signed. @Archethect

[Archethect]

@Archethect Can you sign your commits? so we can merge this PR! thanks

Verified/Signed my last noop commit. Let me know if this is good to go, or you need me to sign all my previous commits as well. I think if I do that, all other commits will need new signatures because of the rebase though.

We need all the commits signed. @Archethect

@ferrabled @josepchetrit12 I rebased and signed all my commits. Let me know if anything else is required. 🙏

[josepchetrit12]

LGTM!