refactor(ast)!: remove JSXOpeningElement::self_closing field

[overlookmotel]

Remove self_closing field from JSXOpeningElement. Whether the tag is self-closing can be determined by whether the JSXElement has a closing_element or not.

This is advantageous for 2 reasons:

1. Reduce size of JSXOpeningElement by 8 bytes.
2. Make it impossible for self_closing and closing_element fields to get out of sync. Only one source of truth.

[overlookmotel]

• refactor(ast)!: remove JSXOpeningElement::self_closing field #10275 👈 (View in Graphite)
• 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 #10275 will not alter performance

_{Comparing 04-06-refactor_ast_remove_jsxopeningelement_self_closing_field (a26fd34) with main (78f1b3a)}

Summary

✅ 36 untouched benchmarks

[overlookmotel]

+1% improvement on parser[RadixUIAdoptionSection.jsx] benchmark. I believe the -1% regression on 2 other benchmarks are just due to noise.

[overlookmotel]

Merge activity

• Apr 7, 10:26 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Apr 7, 10:26 AM EDT: overlookmotel added this pull request to the Graphite merge queue.
• Apr 7, 10:34 AM EDT: Merged by the Graphite merge queue.