Reduce the packages and improve package dependency for 4.x

[nazarhussain]

Below is the packages dependency graph for the 4.x.

There are few points to observe:

1. Almost all the packages which are using web3-core also using web3-common.
2. Rest of the packages have very clear an distinctive domain and separation of concern
3. But these two packages web3-core and web3-common have overlapping and blurred scope.

My recommendations are:

1. To merge web3-common into web3-core.
2. As the web3-core is already published and known to users and web3-common is a new package.
3. There should not be any default export from the package web3-core so we can use distinctive components we need.
4. Because of improved tree shaking there will not be the impact for the users of the package

The following change will bring this value:

1. Remove a package from dependency graph
2. Clear any confusion between scope of web3-core and web3-common packages

We should make this change before 4.x alpha release so people can start migrating their projects would have least impact afterwards.

[nazarhussain]

You can find more findings about this discussion here #5243 (comment)

[nazarhussain]

The action points for this discussion has been resolved with this PR #5262