Normative: make EnumerableOwnPropertyNames ordered

[bakkot]

Related to proposal-for-in-order. Added as a separate PR because this change wasn't technically in scope during the process for that proposal. Thanks to @domenic for bringing this to my attention.

EnumerableOwnPropertyNames is used by Object.keys, Object.values, Object.entries, JSON.parse, and JSON.stringify.

Removing this line has the effect of requiring those to be ordered the same way as Reflect.ownKeys, which is fully specified, rather than for-in, which is only partially specified.

I have not been able to find cases where implementations order any of the APIs which use EnumerableOwnPropertyNames differently than they would Reflect.ownKeys, even in the presence of exotic objects and accessors which modify the object being iterated. So removing this line should not have any effects on the implementations I have on hand.

I want to make this change for two reasons:

1. It removes a case where implementations are permitted to differ, and
2. This line is incredibly confusing anyway, since it is impossible for an implementation to know how the "the Iterator that would be returned if the EnumerateObjectProperties internal method were invoked with O" would behave without actually invoking it, which can have arbitrary other side effects.

[devsnek]

begone evil prose