Remove --harmony-* flags for new Object static methods

test/mjsunit/object-entries.js

Index: test/mjsunit/object-entries.js
diff --git a/test/mjsunit/harmony/object-entries.js b/test/mjsunit/object-entries.js
similarity index 99%
rename from test/mjsunit/harmony/object-entries.js
rename to test/mjsunit/object-entries.js
index 101988a052520287df361de21d8bb642866796fd..71f121b896cc2d6a386a2ea0874bdfecdb81430d 100644
--- a/test/mjsunit/harmony/object-entries.js
+++ b/test/mjsunit/object-entries.js
@@ -2,7 +2,6 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-// Flags: --harmony-object-values-entries
 // Flags: --allow-natives-syntax

[caitp, 2016/10/31 21:37:20]

Don't we normally put these in the es6/ or es7/ or whatever subdirectories when
shipping or removing the flag? Or has that convention disappeared?

[adamk, 2016/10/31 21:39:46]

You caught me :)

I couldn't remember which version these features were in. If you can tell me
which version it'll be I can move them, but I think this may be more bookkeeping
than it's worth. Interested in hearing if you feel this distinction is still
useful.

[caitp, 2016/10/31 22:11:23]

They've all missed the 7.0 boat, which puts them at... ECMA2016? I think it's
fine to put them in the es7  folder though, since that's how most people think
of them

 
 function TestMeta() {