Bump @types/bn.js dependency to 5.1.1

[wbt]

Description

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.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Checklist for 1.x:

• 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.
• [n/a] 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 dtslint with success and extended the tests and types if necessary.
• I ran npm run test:cov and my test cases cover all the lines and branches of the added code. [n/a and ERROR: The filename, directory name, or volume label syntax is incorrect.]
• I ran npm run build with success.
• I have tested the built 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.

[coveralls]

Pull Request Test Coverage Report for Build 3500685412

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+2.3%) to 74.555%

---

Totals
Change from base Build 3490104649:	2.3%
Covered Lines:	3281
Relevant Lines:	4145

---

💛 - Coveralls

[wbt]

The error is a timeout in connecting to Infura, and I don't (on this project) have privileges to force a re-run of a job with the same code, nor do I have a high opinion of adding extraneous commits to PRs that make it less focused.

[github-actions]

This PR has been automatically marked as stale beacause it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment.

[wbt]

Again, it's only stale because I don't have permissions on this project to retrigger a job that failed due to an Infura timeout.

[jdevcs]

merged #5885 into 1.x for these changes