https://github.com/ruby/syntax_suggest/commit/a81b92fcf2

[Bug #21847]

The reason this logic for different methods branches in the class instead of internally was to be eagerly aggressive about runtime performance. This code is currently only used once for the document where it's invoked ~N times (where N is number of lines):

```ruby
module SyntaxSuggest
  class CleanDocument
    # ...
    def join_trailing_slash!
      trailing_groups = @document.select(&:trailing_slash?).map do |code_line|
        take_while_including(code_line.index..) { |x| x.trailing_slash? }
      end
      join_groups(trailing_groups)
      self
    end
```

Since this is not currently a hot-spot I think merging the branches and using a case statement is a reasonable tradeoff and avoids the need to do specific version testing.

An alternative idea was presented in #241 of behavior-based testing for branch logic (which I would prefer), however, calling the code triggered requiring a `DelegateClass` when the `syntax_suggest/api` is being required.

https://github.com/ruby/syntax_suggest/commit/ab122c455f

It used to not emit this token type, but now it does.
So when a newer version of prism is present, we can fall back
to the same code that ripper uses.

Ref:
* https://github.com/ruby/ruby/pull/15914
* https://github.com/ruby/prism/pull/3859

https://github.com/ruby/syntax_suggest/commit/42a3b8f6cb

https://github.com/ruby/syntax_suggest/commit/54bb8ab330

https://github.com/ruby/syntax_suggest/commit/ce7b87184e

https://github.com/ruby/syntax_suggest/commit/ea73ed586a

	[PATCH] [ruby/timeout] Compatibility with Fiber scheduler. (https://github.com/ruby/timeout/pull/97)

	[Bug #21947]

	https://github.com/ruby/timeout/commit/55d7c84b50

	[PATCH] YJIT: Fix not reading locals from `cfp->ep` after `YJIT.enable` and exceptional entry
	MIME-Version: 1.0
	Content-Type: text/plain; charset=UTF-8
	Content-Transfer-Encoding: 8bit

	Fix for [Bug #21941].

	In case of `--yjit-disable`, YJIT only starts to record environment
	escapes after `RubyVM::YJIT.enable`. Previously we falsely assumed that
	we always have a full history all the way back to VM boot. This had YJIT
	install and run code that assume EP=BP when EP≠BP for some exceptional
	entry into the middle of a running frame, if the environment escaped
	before `YJIT.enable`.

	The fix is to reject exceptional entry with an escaped environment.
	Rename things and explain in more detail how the predicate for deciding
	to assume EP=BP works. It's quite subtle since it reasons about all
	parties in the system that push a control frame and then run JIT code.

	Note that while can_assume_on_stack_env() checks the currently running
	environment if it so happens to be the one YJIT is compiling against, it
	can return true for any ISEQ. The check isn't necessary for fixing the
	bug, and the load bearing part of this patch is the change to
	exceptional entries.

	This fix is flat on speed and space on ruby-bench headline benchmarks.

	Many thanks for the community effort to create a small test case for
	this bug.