Test file includes are merged with universal includes in the wrong order #34
Description
test262 INTERPRETING.md, file specific includes must be evaluated "prior to test execution, after the files listed in the Test262-Defined Bindings section [harness/assert.js and then harness/sta.js] and the file listed for the async flag below" (emphasis mine). But builder.js appends those universal files to the file-specific includes, resulting in the wrong order.