Fix validation uint int sizes

[fullkomnun]

Description

Previously an ABI that contained a numeric type (int/uint) of size that is not a power of 2 (such as uint40, int24) would result in the validator / check function being set on Zod as undefined and lead to a cryptic TypeError during validation.
I have setup validators for all valid numeric type sizes ([u]int8, [u]int 16, ... , [u]int256) and throw an error right away if during conversion of JSON scheme to Zod an unsupported type is encountered.
Generated 'single parameter' ABI test cases for all valid sizes.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run lint with success and extended the tests and types if necessary.
• I ran npm run test:unit with success.
• I ran npm run test:coverage and my test cases cover all the lines and branches of the added code.
• I ran npm run build and tested dist/web3.min.js in a browser.
• I have tested my code on the live network.
• I have checked the Deploy Preview and it looks correct.
• I have updated the CHANGELOG.md file in the root folder.
• I have linked Issue(s) with this PR in "Linked Issues" menu.

[codecov]

Codecov Report

Merging #6434 (30ab555) into 4.x (226b3ba) will increase coverage by 0.00%.
The diff coverage is 92.85%.

Additional details and impacted files

@@           Coverage Diff           @@
##              4.x    #6434   +/-   ##
=======================================
  Coverage   89.67%   89.67%           
=======================================
  Files         214      215    +1     
  Lines        8222     8234   +12     
  Branches     2223     2224    +1     
=======================================
+ Hits         7373     7384   +11     
- Misses        849      850    +1     

Flag	Coverage Δ
UnitTests	89.67% <92.85%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
web3	∅ <ø> (∅)
web3-core	∅ <ø> (∅)
web3-errors	∅ <ø> (∅)
web3-eth	∅ <ø> (∅)
web3-eth-abi	∅ <ø> (∅)
web3-eth-accounts	∅ <ø> (∅)
web3-eth-contract	∅ <ø> (∅)
web3-eth-ens	∅ <ø> (∅)
web3-eth-iban	∅ <ø> (∅)
web3-eth-personal	∅ <ø> (∅)
web3-net	∅ <ø> (∅)
web3-providers-http	∅ <ø> (∅)
web3-providers-ipc	∅ <ø> (∅)
web3-providers-ws	∅ <ø> (∅)
web3-rpc-methods	∅ <ø> (∅)
web3-utils	∅ <ø> (∅)
web3-validator	∅ <ø> (∅)

[avkos]

LGTM. Thanks for your contribution

[jdevcs]

Thanks for contribution

[jdevcs]

Same in this PR , update is required to fix Conflicting file, I'll merge PR after it, Thanks

[jdevcs]

unit test not passing

[fullkomnun]

unit test not passing

Checking

[CodeLikeLisa]

is the solution to use an older version of web3js?

[luu-alex]

Hey there im looking into an issue. @fullkomnun theres an inconsistent integration test failing in the pipelines and i think it stems from the last PR you pushed. The abi and the testcase that is failing. any ideas?

[jdevcs]

codecov/patch Failing after 1s — 66.66% of diff hit (target 89.88%)

[luu-alex]

@luu-alex update, it seems to be an eventslog issue. not related to PR

[jdevcs]

codecov/patch Failing after 1s — 66.66% of diff hit (target 89.88%)

@fullkomnun

[Muhammad-Altabba]

Looks good, thanks,
I just have suggestions for the error string...

[ngmachado]

Any news about this PR?

[luu-alex]

@ngmachado will be merged in today