fix(lexer): restore debug assert in Lexer::finish_next

[overlookmotel]

#11204 removed a debug_assert! from Lexer::finish_next which checks that end of a Token is always >= start.

I assume this was unintentional, as this check is useful for making sure lexer is operating correctly in conformance tests. Restore it.

[overlookmotel]

• fix(lexer): restore debug assert in Lexer::finish_next #11208 👈 (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.

[overlookmotel]

@Boshen I assume removing it was unintentional?

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #11208 will not alter performance

_{Comparing 05-21-fix_lexer_restore_debug_assert_in_lexer_finish_next_ (74b405d) with main (8e8dea5)}

Summary

✅ 38 untouched benchmarks

[Boshen]

It's checked here

oxc/crates/oxc_parser/src/lexer/token.rs

Line 99 in 6e9de84

debug_assert!(end >= start, "Token end ({end}) cannot be less than start ({start})");

[overlookmotel]

Oh sorry I completely missed that.