Editorial: Use CreateDataPropertyOrThrow abstract op in more places

[shvaikalesh]

A step like ! CreateDataProperty(...) asserts only that [[DefineOwnProperty]] is an ordinary method that can't throw, but doesn't assert that property creation is a guaranteed success because [[DefineOwnProperty]] only returns boolean status (it is Object.defineProperty that throws a TypeError).

This change replaces these steps with ! CreateDataPropertyOrThrow(...), asserting that property is defined successfully since all its call sites operate on newly-created objects with no non-configurable properties.

ECMA-262 has no occurrences of ! CreateDataProperty(...).

Also, this change replaces "Call" with "Perform", which is a new convention of ECMA-262.

---

Preview | Diff

[domenic]

I still see the following; should we change them too?

• https://whatpr.org/webidl/1359.html#ref-for-sec-createdataproperty
• https://whatpr.org/webidl/1359.html#ref-for-sec-createdataproperty%E2%91%A0

[shvaikalesh]

@domenic Oh no, https://whatpr.org/webidl/1359.html#ref-for-sec-createdataproperty asserts on the result, so it's semantically equivalent to ! CreateDataPropertyOrThrow(...), while for https://whatpr.org/webidl/1359.html#ref-for-sec-createdataproperty%E2%91%A0 I have a different change in mind: #1360.