JSON 5 , Decode URI, Types BN, and Loder Utils updates

[jdevcs]

Look in following PRs and apply libs update in manual PR where required :

• JSON 5

• Bump json5 from 1.0.1 to 1.0.2 #5723

• Bump json5 from 2.2.1 to 2.2.3 in /packages/web3-eth2-beaconchain #5722

• Bump json5 from 2.2.1 to 2.2.3 in /packages/web3-eth2-core #5721

• Decode URI

• Bump decode-uri-component from 0.2.0 to 0.2.2 in /packages/web3-eth2-beaconchain #5678

• Bump decode-uri-component from 0.2.0 to 0.2.2 #5676

• Types BN

• Bump @types/bn.js dependency to 5.1.1 #5640

• Loder Utils

• Bump loader-utils from 1.4.0 to 1.4.2 #5633

[jdevcs]

@types/bn.js dependency to 5.1.1 : as mentioned

This PR sets a higher minimum version for the @types/bn.js dependency. In version 5.1.1, a new divmod function was added which is a breaking change on a patch version number release: a type defined from an import of @types/bn.js@v5.1.1 is not compatible with the BN type if defined from an import of @types/bn.js@v5.1.0.

Because the current loose specification allows either version to be used, sometimes NPM picks different versions for different web3 package or even for the same package directly vs. when included in another web3 package. This incompatibility causes code that previously worked fine due to type consistency to now fail compilation. Pinning all to .0 exactly would be less likely to cause breaking changes elsewhere or in the future, as maintainers of the typing package seem to not recognize this breaking change as such and could do something similar in the future. However, pinning to .0 would likely cause greater incompatibilities unless all projects which use web3 and have type interaction with the BN type also pin to .0 specifically, and the ^ notation is more common. As long as everything is consistent, it works, and failing forward makes a little more sense.