Fix development build scripts

[rekmarks]

#14583 broke the development build scripts (e.g. yarn start) by adding a positional argument to a package script (build:dev) that is used and passed positional arguments in the build script itself. This PR removes the positional argument from the build:dev script and yarn start now works again. In addition, the --apply-lavamoat flag is properly forwarded to child processes, which was not the case in the original implementation.

To test, yarn start should work and LavaMoat should not be applied, in distinction to yarn build:dev dev --apply-lavamoat=true. Whether LavaMoat is applied can be determined by checking whether Object.isFrozen(Object.prototype) is true (with LavaMoat) or false (without LavaMoat).

[jpuri]

Tested by running yarn start locally and works well.

[dan437]

Awesome, yarn start works now and there is no white screen after opening the extension. Thank you!

[brad-decker]

@rekmarks @dan437 rebasing on develop now that the fix for the e2e test failure has landed

[metamaskbot]

Builds ready [25d6583]

• builds: chrome, firefox, opera
• builds (beta): chrome, firefox, opera
• builds (flask): chrome, firefox, opera
• build viz: Build System
• code coverage: Report
• storybook: Storybook
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8
  • content-script: 0
  • contentscript: contentscript
  • disable-console: disable-console
  • inpage: inpage
  • phishing-detect: phishing-detect
  • policy-load: policy-load
  • sentry-install: sentry-install
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (1809 ± 41 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	87	1784	196	365	175
		domContentLoaded	1618	1904	1764	70	34
		load	1646	1998	1809	85	41
		domInteractive	1618	1904	1764	70	34