Fix: rm console.warn if scrypt not present

[CruzMolina]

🙏

[coveralls]

Coverage decreased (-0.08%) to 83.107% when pulling c6aa8fb on CruzMolina:patch-1 into 7d1b0ea on ethereum:1.x.

[gnidan]

Yes, please!

[michaelsbradleyjr]

Already done in #3035, #3036. That warning is now only printed when installing web3.

I'm about to make a PR for the web3-js/scrypt-shim repo that will remove the runtime warning in the event of maxmem exceptions, since the true reason those may arise is now understood. I will also make a PR for this repo to remove the static tests (copied from go-ethereum's repo) that contain invalid kdf parameters.

[michaelsbradleyjr]

Quick update on improvements to scrypt-shim: https://github.com/web3-js/scrypt-shim/compare/master...michaelsbradleyjr:refactor-per-rfc?expand=1.

I've done my best to be super-attentive to edge cases and whatnot. Last thing is to get the test suite into proper shape. PRs #3035, #3036 will be updated once that work is complete and the PR has been submitted for scrypt-shim.

[nivida]

I'm closing this PR because of the mentioned PRs for 1.x and 2.x from @michaelsbradleyjr