fix(parser): error when } and > appear in JSXText

[Boshen]

closes #9770

[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.

[codspeed-hq]

CodSpeed Performance Report

Merging #9777 will not alter performance

_{Comparing 03-14-fix_parser_error_for_and_in_jsxtext_ (a113f7e) with main (ea7e3f0)}

Summary

✅ 33 untouched benchmarks

[overlookmotel]

Merge activity

• Mar 17, 9:31 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 17, 9:31 AM EDT: A user added this pull request to the Graphite merge queue.
• Mar 17, 9:37 AM EDT: A user merged this pull request with the Graphite merge queue.

[overlookmotel]

I had to remind myself how the byte_search! macro works!

@Boshen Was confused by the change to this method. Was this an unrelated bug in codegen?

oxc/crates/oxc_codegen/src/gen.rs

Lines 2580 to 2584 in a113f7e

	fn r#gen(&self, p: &mut Codegen, _ctx: Context) {
	p.print_str("{...");
	p.print_expression(&self.expression);
	p.print_ascii_byte(b'}');
	}