Now we can remove the close event

[antonio-fr]

and only let disconnect.
Following #4786

Description

Close event can now be removed. It is a deprecated event that is replaced by disconnect.
Type of change

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

It was just a deprecation warning.

Checklist

[y] I have selected the correct base branch.
[y] I have performed a self-review of my own code.
[y] I have commented my code, particularly in hard-to-understand areas.
[n] I have made corresponding changes to the documentation.
[y] My changes generate no new warnings. And one warning less
[?] Any dependent changes have been merged and published in downstream modules.
[n] I ran npm run dtslint with success and extended the tests and types if necessary.
[n] I ran npm run test:unit with success.
[n] I ran npm run test:cov and my test cases cover all the lines and branches of the added code.
[n] I ran npm run build and tested dist/web3.min.js in a browser.
[n] I have tested my code on the live network.
[n] I have checked the Deploy Preview and it looks correct.
[n] I have updated the CHANGELOG.md file in the root folder.

[nazarhussain]

@antonio-fr Please provide some reference for that standard change.

[coveralls]

Pull Request Test Coverage Report for Build 1941142164

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 286 unchanged lines in 10 files lost coverage.
• Overall coverage increased (+1.8%) to 74.497%

---

Files with Coverage Reduction	New Missed Lines	%
packages/web3-core-requestmanager/src/jsonrpc.js	1	70.0%
packages/web3-core-helpers/lib/errors.js	2	79.41%
packages/web3-core-subscriptions/lib/subscription.js	2	90.37%
packages/web3-core-helpers/src/formatters.js	7	85.42%
packages/web3-core-requestmanager/lib/index.js	17	72.89%
packages/web3-core-helpers/src/errors.js	29	1.56%
packages/web3-utils/src/soliditySha3.js	34	3.43%
packages/web3-utils/src/index.js	43	31.38%
packages/web3-utils/src/utils.js	44	9.66%
packages/web3-eth-accounts/src/index.js	107	23.67%

Totals
Change from base Build 1927230259:	1.8%
Covered Lines:	3238
Relevant Lines:	4102

---

💛 - Coveralls

[antonio-fr]

As describe in the initial related issue opened, Metamask informs that The event 'close' is deprecated and may be removed in the future. Please use 'disconnect' instead. For more information, see: https://eips.ethereum.org/EIPS/eip-1193#disconnect

This current PR was proposed by @jdevcs who wrote to me in the issue "go ahead and open PR for removing close".

The base working standard is EIP1193. This standard is the new Web3 standard, and it states there's a disconnect event, but no "close" event. The "close" event was deprecated by the PR #2586 in the EIP1193, which deprecated "close" in favor of "disconnect. The EIP1193 since clearly states :
Legacy Events : close (DEPRECATED) This event is superseded by "disconnect".

[jdevcs]

Many Thanks @antonio-fr for your contribution. Created #4839 as some tests were failing in this PR's github actions.