feat(forge build): add initcode size check

[mgiagante]

Closes #4783
described in the Additional Context of this comment

Motivation

Prior to EIP-3860 there was no size limit on creation code (initcode), and just a 24576 byte size limit on runtime code.
EIP-3860 went live in Shangai so now there is both:

• a 24576 byte size limit on runtime code
• a new 24576 * 2 = 49152 byte size limit on initcode.

Currently, forge build --sizes does not account for this new size limit.

Solution

1. This PR adds a new column pair to the table displayed by forge build --sizes for the contract init code size (bytes) and the margin left counting towards the limit (bytes).
2. Also, the existing check for the deployed contract size is complemented with a new check for the init code size, making the process exist with status code 1 if the check fails.
3. Finally, a new option --ignore-eip-3860 allows to ignore the check mentioned in the previous point. This is aimed to users deploying to chains that do not enforce this limit.

Testing

• Two tests were adjusted to account for the new structure of the table.
• Two new tests were introduced to verify both failing and ignoring the new init code size limit.

[NelsonGaldeman]

Finally! Thank you ser 🫡

Tested and worked to me!

[grandizzy]

Thank you! looks good, have added minor nits

[grandizzy]

thank you, lgtm! Pending other review

[zerosnacks]

Thanks! Looks good 👍

[mgiagante]

@DaniPopes Please let me know if this needs any further improvements before it can be merged. Thank you!

[DaniPopes]

Thanks!