Import test changes from JavaScriptCore

[javascriptcore-test262-automation] Updated curation log with latest revision sha's from export and changed files.
    sourceRevisionAtLastExport: 5895364ed5 targetRevisionAtLastExport: df1fc484

[javascriptcore-test262-automation] Changes from https://github.com/webkit/webkit.git at sha 5895364ed5 on Fri Aug 03 2018 18:02:54 GMT+0000 (Coordinated Universal Time)

These are not spec tests neither identify points not already covered in the tests to cover something new from the specs

I observed each file in each of these folders and they don't contain any test matching for specific parts of ECMAScript, without a specific place for Test262.

Ref https://github.com/bocoup/test262-automation/pull/76

Import test changes from JavaScriptCore

[javascriptcore-test262-automation] Updated curation log with latest revision sha's from export and changed files.
    sourceRevisionAtLastExport: 00228d3ccc targetRevisionAtLastExport: 4314e2ca

[javascriptcore-test262-automation] Changes from https://github.com/webkit/webkit.git at sha 00228d3ccc on Mon Jul 30 2018 18:01:10 GMT+0000 (Coordinated Universal Time)

Fixes #1640
Closes #1652

[javascriptcore-test262-automation] Updated curation log with latest revision sha's from export and changed files.
    sourceRevisionAtLastExport: 8bfa53d50 targetRevisionAtLastExport: 8bc4e38a

The specification was updated in https://github.com/tc39/ecma402/pull/232.

Make doneprinthandle.js accept the input and produce the output expected by test262-harness. (#1650)

This is not a breaking change, it simply adds explicit handling to the function

Generate tests for "feature new.target"

Merge branch 'feature-new.target' of https://github.com/IgnoredAmbience/test262 into IgnoredAmbience-feature-new.target

* 'feature-new.target' of https://github.com/IgnoredAmbience/test262:
  Add feature flags for `new.target`

Additionally removed the `arrow-function` feature for
test/language/eval-code/direct/new.target-fn.js as it is not testing
arrow-functions, but they are mentioned in the preamble.

Curation: Removed all test files that depend on $vm (implementation-contributed/javascriptcore) (#1629)

- Eliminates:
  - controlFlowProfiler/*
  - exceptionFuzz/*

Follow up to https://github.com/tc39/test262/pull/1643

All other Proxy tests use the syntax `attr: function() {...}` for
defining traps, ownKeys was unique in using the shorthand syntax. Change
to longhand syntax for back-compat for partial implementations.

Proxy/deleteProperty/boolean-trap-result-boolean-true.js was missing a
feature flag for the Reflect library.

Thsi test for the parsing of string literals was expressed using `eval`.
This made the test more complex than necessary and also prevented the
test from providing value to ECMAScript parsers.

Remove the use of `eval` and instead express the expectation with
literal source text.

This test is technically valid because it does trigger a SyntaxError in
conforming runtimes. However, it was authored and documented to test
LegacyOctalEscapeSequence, but due to an apparent typo, it actually
demonstrates an unrelated parsing error.

Because 'legacy-octal-escape-sequence-stricts.js' sufficiently tests the
restriction on LegacyOctalEscapeSequence, remove this test rather than
correct it.

This test for string literals asserts the restriction on
LegacyOctalEscapeSequence in strict mode. It is not sufficiently
distinct from the test 'legacy-octal-escape-sequence-stricts.js' to
warrant inclusion in the test suite. Because that test includes much
more thorough documentation, it should be preferred.