feat: go-to-def and find-references on control-flow keywords

[roife]

fix #17517.

This PR implements go-to-definition and find-references functionalities for control flow keywords, which is similar to the behaviors in the highlight-related module. Besides, this PR also fixes some incorrect behaviors in highlight-related.

Changes

1. Support for go-to-definition on control flow keywords:
   This PR introduces functionality allowing users to navigate on the definition of control flow keywords (return, break, continue).
   Commit: 2a3244e..7391e7a.

2. Bug fixes and refactoring in highlight-related:

   • Handling return/break/continue within try_blocks:
     This PR adjusted the behavior of these keywords when they occur within try_blocks. When encounter these keywords, the program should exit the outer function or loop which containing the try_blocks, rather than the try_blocks itself; while the ? will cause the program to exit try_blocks.
     Commit: 59d697e.
   • Support highlighting keywords in macro expansion for highlight-related:
     Commit: 88df24f.
   • Detailed description for the bug fixes
     • The previous implementation of preorder_expr incorrectly treated try_blocks as new contexts, thereby r-a will not continue to traverse inner return and break/continue statements. To resolve this, a new function preorder_expr_with_ctx_checker has been added, allowing users to specify which expressions to skip.
       • For example, when searching for the ? in the context, r-a should skip try_blocks where the ? insides just works for try_blocks. But when search for the return keyword, r-a should collect both the return keywords inside and outside the try_blocks
     • Thus, this PR added WalkExpandedExprCtx (builder pattern). It offers the following improvements: customizable context skipping, maintenance of loop depth (for break/continue), and handling macro expansion during traversal.

3. Support for find-references on control flow keywords:
   This PR enables users to find all references to control flow keywords.
   Commit: 9202a33.

[Veykril]

One thing to look out for is the turning FileRange into TextRange after upmapping. All of those need to verify that the file id of the FileRange is in fact the same as the file we are doing the feature stuff in, as include! has its input in a different file than where the call is. Generally speaking, dropping the file id of a FileRange yielded from upmapping without checks can easily cause issues

[roife]

I squashed some commits related to goto-def and updated the PR description for simplicity.

@rustbot label -S-waiting-on-author +S-waiting-on-review

[bors]

☔ The latest upstream changes (presumably #17620) made this pull request unmergeable. Please resolve the merge conflicts.

[Veykril]

@bors r+

[bors]

📌 Commit f027a46 has been approved by Veykril

It is now in the queue for this repository.

[bors]

⌛ Testing commit f027a46 with merge d092f7d...

[bors]

☀️ Test successful - checks-actions
Approved by: Veykril
Pushing d092f7d to master...