Browser simulateScript - restore build

[ernest-nowacki]

https://smartcontract-it.atlassian.net/browse/FRONT-3851

Hey while debugging Firefox issues with simulate script I digged up the above ticket. During our initial implementation I've built simulateScript for frontend usage once and copied the output to our front end repo. While it got us moving now when we have package published I believe we could be using proper way.

There are few things happening here:

1. I've noticed here webpack and all dependencies required to build frontend simulate script has been removed: a1c811d

Is that the intention? I could still see package.json script having build:browser script (which wasn't working anymore).

In this PR I'm restoring everything needed to build that simulate package. I noticed repo started using yarn so I adjusted PR for that (no more package-lock.json). All dependencies required to build front end shouldn't end up being shipped in the package as they are dev dependencies. If however it's still no longer the business of functions-toolkit package to build front end simulator I might try to extract building process somewhere else.

2. There was build error reported by webpack when building simulator:

That's because it couldn't handle the dynamic nature of allowed modules. I refactored this part of the code a bit to make sure there are no warnings during the build. This shall affect only browser simulator not deno version.

[KuphJr]

Thanks @ernest-nowacki ! My only comment is we are now below our required test coverage threshold. We should either add tests, or at the very least ignore these files in Jest such that our workflows pass before merging.

[ernest-nowacki]

Hey @KuphJr thanks for checking the PR!

I had one error in unit tests + I noticed other tests are living under test directory. Fixing those issues get me back to 100% coverage on new addons 👍 .

[cl-sonarqube-production]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication