refactor(ast/estree): re-order fields in visitation order

[overlookmotel]

Re-order fields in ESTree and TS-ESTree ASTs to be in visitation order (which is the order in which they're defined in Rust types).

This does not align with either Acorn or TS-ESLint, but for the reasons discussed in #9705 (comment), I feel this isn't a concern. The field order doesn't matter much per se, only that it's consistent, and this change has other benefits - it will make it simpler to build a visitor which visits fields in the correct order, and allows adding other parsers to acorn-test262 in order to produce test cases for decorators.

Visitation order aligns with TS-ESLint except for the following types:

• ExportSpecifier
• TSImportType
• TSIndexedAccessType
• TSMethodSignature
• TSPropertySignature
• TSTypePredicate

In these 6 cases, TS-ESLint's visitorKeys has the wrong visitation order, because it does not visit fields in source order. I will open an issue and hopefully they can fix.

This PR also bumps acorn-test262 to include oxc-project/estree-conformance#37 which re-orders the fields in fixture snapshots to match the new field order here.

[overlookmotel]

• refactor(ast/estree): re-order fields in visitation order #11362 👈 (View in Graphite)
• refactor(ast_tools/estree): order type and span fields first by default #11361
• refactor(ast/estree): do not put TS struct fields last #11360
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #11362 will create unknown performance changes

_{Comparing 05-28-refactor_ast_estree_re-order_fields_in_visitation_order (12690a1) with 05-28-refactor_ast_tools_estree_order_type_and_span_fields_first_by_default (1d1ebd6)}

Summary

🆕 38 new benchmarks

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
🆕	codegen[RadixUIAdoptionSection.jsx]	N/A	132.2 µs	N/A
🆕	codegen[binder.ts]	N/A	4.8 ms	N/A
🆕	codegen[cal.com.tsx]	N/A	38.9 ms	N/A
🆕	codegen[react.development.js]	N/A	2.2 ms	N/A
🆕	formatter[RadixUIAdoptionSection.jsx]	N/A	298.7 µs	N/A
🆕	formatter[binder.ts]	N/A	18.9 ms	N/A
🆕	formatter[cal.com.tsx]	N/A	142.7 ms	N/A
🆕	formatter[react.development.js]	N/A	9.2 ms	N/A
🆕	lexer[RadixUIAdoptionSection.jsx]	N/A	21.1 µs	N/A
🆕	lexer[binder.ts]	N/A	929.3 µs	N/A
🆕	lexer[cal.com.tsx]	N/A	5.8 ms	N/A
🆕	lexer[react.development.js]	N/A	383.6 µs	N/A
🆕	linter[RadixUIAdoptionSection.jsx]	N/A	2.8 ms	N/A
🆕	linter[binder.ts]	N/A	148.6 ms	N/A
🆕	linter[cal.com.tsx]	N/A	1.3 s	N/A
🆕	linter[react.development.js]	N/A	54.4 ms	N/A
🆕	mangler[RadixUIAdoptionSection.jsx]	N/A	14.2 µs	N/A
🆕	mangler[binder.ts]	N/A	811.2 µs	N/A
🆕	mangler[cal.com.tsx]	N/A	3 ms	N/A
🆕	mangler[react.development.js]	N/A	282.7 µs	N/A
...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

[Boshen]

Merge activity

• May 29, 2:20 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• May 29, 2:20 AM UTC: Boshen added this pull request to the Graphite merge queue.
• May 29, 2:28 AM UTC: Merged by the Graphite merge queue.