Class fields with the same name

Fixes #1355 

The tests are explicitly for bad hex chars at certain indexes, and that
rogue `%` was giving false positives.

The change is done in the following patch, where default options
have a null prototype. This matches what other Intl objects have.
https://github.com/tc39/proposal-intl-plural-rules/commit/1abe8af440fb47d888ace701e8a46559bdbe7b06

Added missing cases into BigIntConstructor with String parameters

Fix #1345

Originally discovered by Cait Potter (@caitp), reported in irc.mozilla.org#jslang

- Add tests for multiple public fields of the same name
- Reorganize fields default templates
- Add more tests for redeclaration of fields
- Remove non used template
- Add tests for computed property names in class fields definitions
- Minor test fixes

Thanks @andresaraujo for helping with the early review

* Accessing `ta[0]` throws a TypeError.

* Fix array indices starting at 0 and property references

* Fix classfields templates for properly checking static propnames.

* Generate tests

* `assert.equal` is not defined

* Add missing includes

* Generate tests

* typo s/Avalue/42/

* fix whitespace

* Add missing var for strict mode

* Expand generated class fields tests for forbidden computed property name values

Ref https://github.com/tc39/test262/pull/1339#issuecomment-342830243

* derived classes have access to private names in base classes, if private names are in scope

classfields: Tests for modified algorithms and Private Names

Add tests for setting/defining an element of a typed array to a value, where converting that value to the typed array element type detaches the buffer underlying the typed array. (#1336)

fixup: swap actual and expected in test/built-ins/Promise/prototype/finally/species-symbol.js (#1333)

classfields: add tests duplicate private fields and deleting private fields

classfields: add tests for privatename production and ASI

classfields: add early error tests for privatename references

classfields: add tests for forbidden public/private propertynames

Fix multiple test issues

Changes:

- Changed eval-err-contains-supercall-1.case to add a property access similar to eval-err-contains-supercall-2.case, without this property access eval-err-contains-supercall-1.case would be identical to eval-err-contains-supercall.case.
- Remove unnecessary "earlyerror" and "executionerror" template arguments when the value is already clear from the context.
- Fixed the description in eval-err-contains-supercall-2.case to refer to the correct early error rule.
- Fixed a copy-paste error in eval-err-contains-superproperty-1.case and eval-err-contains-superproperty-2.case.
- Split initializer-eval-super into initializer-eval-super-call and initializer-eval-super-property, because we actually need to test different behaviour for the super-call compared to the super-property case.
- Split initializer-eval into initializer-eval-arguments and initializer-eval-newtarget, because `arguments` and `new.target` are differently handled in class-fields.
- And fixed other copy-paste errors in the template files.

Fixes #1325

Fixes #1313

Fixes #1312

Fixes #1306

Only this test relied on $ERROR throwing a catchable Test262Error.

This change allows test environments to provide their on $ERROR function for better error reporting.

Promise.p.finally: test SpeciesConstructor and Symbol.species lookup

Bigint fixups

getBigUint64 tests

setBigInt64 tests