Simpler provider parameter handling on construction of a Web3 Module

[nivida]

Description

The goal of this PR is to simplify the provider handling. Currently, there are too many different possibilities we provide from the Web3.js library. In the future, there should be one clear path of how Web3.js should get initiated with the provider.

Related issues:
#2275

Type of change

• Enhancement

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 warnings.
• I have updated or added types for all modules I've changed
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run test in the root folder with success and extended the tests if necessary.
• I ran npm run build in the root folder and tested it in the browser and with node.
• I ran npm run dtslint in the root folder and tested that all my types are correct
• I have tested my code on the live network.

[zachlysobey]

Its a little concerning that the lockfile would change like it does here without any corresponding changes to package.json, etc... Any idea what'd going on here?

[nivida]

This is because I've done a clean install and deleted all the package-lock.json files before. Will finish this work and release it ~beta.45