fix(estree): Ensure the same key order for AssignmentPattern

[leaysgur]

Part of #9705

With this PR, all AST nodes now have a consistent key order for each node type.
(Checked by https://github.com/leaysgur/oxc_estree_ts-ast-diff-viewer/blob/main/scripts/verify-key-order-oxc.js)

Except for:

• Literal: regex and bigint keys
• TSModuleDeclaration: body key is missing when declare module "jq";

[graphite-app]

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.

[Copilot]

Pull Request Overview

This PR standardizes the key ordering in various AST node serializers to ensure consistency across the codebase.

• Reorders fields in BindingRestElement, FormalParametersRest, ArrowFunctionExpressionBody, and AssignmentTargetPropertyIdentifierValue to align with the expected key order.
• Addresses minor field order discrepancies in TypeScript-specific serialization sections.

Comments suppressed due to low confidence (4)

crates/oxc_ast/src/serialize.rs:613

• [nitpick] The field order is updated here to place 'decorators' before 'optional' for BindingRestElement. Please verify that this ordering is consistent with the established AST node schema.

decorators: [],

crates/oxc_ast/src/serialize.rs:653

• [nitpick] The reordering of 'optional' and 'typeAnnotation' fields in FormalParametersRest now aligns with other nodes. Ensure that this change is reflected in the corresponding documentation or tests.

state.serialize_ts_field("optional", &rest.argument.optional);

crates/oxc_ast/src/serialize.rs:885

• [nitpick] In ArrowFunctionExpressionBody, swapping the order of 'optional' and 'typeAnnotation' matches the desired key order. Confirm that this update does not affect any downstream consumers.

optional: false,

crates/oxc_ast/src/serialize.rs:906

• [nitpick] For AssignmentTargetPropertyIdentifierValue, the new ordering between 'optional' and 'typeAnnotation' improves uniformity. It is recommended to double-check that this ordering change is aligned with the overall AST serialization standards.

state.serialize_ts_field("optional", &False(()));

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #10953 will not alter performance

_{Comparing f/ast-key-order (d57de1a) with main (bed3f47)}

Summary

✅ 36 untouched benchmarks

[overlookmotel]

Thank you!