benchmark: remove es benchmark

[psmarshall]

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

These benchmarks compare the performance of ES6 features and their ES5 equivalents. These are testing the javascript engine itself and not node in any way, as far as I can tell. six-speed does a good job testing these things already, and there is a lot of overlap between these two suites. We also have alerts set up for six-speed on the V8 side so we will see any regressions before they make it into node. I'd suggest removing these benchmarks entirely.

[jasnell]

I'm generally -1 on this but won't block. I use these frequently to test improvements in performance across v8 updates.

[mscdex]

I agree with @jasnell that these benchmarks can still be useful to us.

[Trott]

CI: https://ci.nodejs.org/job/node-test-pull-request/16497/

[BridgeAR]

@jasnell @mscdex If one of these cases is not covered by six-speed, it should be possible to move them over.

Since neither of you is blocking, I still mark this as author-ready.

[Trott]

Resume Build: https://ci.nodejs.org/job/node-test-pull-request/16529/

[joyeecheung]

This PR needs a rebase against master to avoid the git failure in the CI.

[psmarshall]

@jasnell If you are using this frequently then I guess it is worth keeping - I'd argue these types of benchmarks are better suited to external suites like six-speed but I guess in your case, the benefit is having the performance runner within node and getting the numbers out in a format that is useful to you.

[psmarshall]

I'm going to close this given that it is in use. We could revisit it once:

1. We know if there is anything in this suite that is not covered by six-speed
2. There is an easy way to run six-speed for different node versions and compare them