perf: Remove Error.captureStackTrace from all WebpackErrors

[markjm]

Closes ##13532

What kind of change does this PR introduce?
perf fix for errors

Did you add tests for your changes?
current error tests passing

Does this PR introduce a breaking change?
dont think so

What needs to be documented once your changes are merged?
no>

[webpack-bot]

For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

[markjm]

I ran UTs locally, but not sure if I ran all different integration tests. Seems possible that some stack messages may slightly change, but lets see with this test pass

[webpack-bot]

@markjm The most important CI builds failed. This way your PR can't be merged.

Please take a look at the CI results from azure (1 errors / 0 warnings) and appveyor (success) and fix these issues.

[markjm]

Seems one watching test failed. Wondering if its flaky because other node versions both below and above this one are fine

[markjm]

@sokra fyi - patching in this change gave us the 3second per recompile improvement I mentioned in the issue

[sokra]

Thanks