Fixed broken fetch for Node.js > 18.x and fixed double callback

[ghost]

closes #5367, #6380

Description

Fixes #5367

Fixes #6380

https://stackoverflow.com/questions/73817412/why-is-the-agent-option-not-available-in-node-native-fetch

Please merge this PR as it is a CVE level bug for some environment using custom httpAgents ( Internal connections, etc ).

Without this patch, current Web3.js provider running on the latest Node.js LTS version could leak connection outside of the httpAgent proxy connections. ( As it will depend on the global.fetch which doesn't support agents natively )

Type of change

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

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.

[ghost]

Fixed tests for Node.js 16.x version which doesn't have globalThis.fetch by default.