fix: patch the angular browser.js to allow `{crypto: true, stream: …

[joshstevens19]

…true`

Description

When you install web3 on a angular app and try to build with the angular-cli it will not work without writing your own patch script. This is because we have to replace the node:false in the /angular-cli-files/models/webpack-configs/browser.js with node: {crypto: true, stream: true} to allow web3 to work with angular (as they enforce node: false which will not allow web3 to work).

Explained more in here: #2260 (comment)

I have wrote a angular-patch.js script which will run on post-install and handle all this for them. I have checked to make sure it only runs if they are installing web3 within a angular app.

Type of change

• Bug fix
• New feature
• Breaking change

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.