fix(deps): update rust crate lalrpop-util to 0.22.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
lalrpop-util	dependencies	minor	0.20.1 -> 0.22.0

---

Release Notes

lalrpop/lalrpop (lalrpop-util)

v0.22.0

Compare Source

Breaking changes

• The lexer feature no longer implies the std feature. Now lexer is
  usable in no_std environments. In no_std, ParseError only implements the
  Error trait in rust 1.81 or later (since core::error was stablized in 1.81).

Features

• Overhaul cfg attributes. You can now include or omit grammar rules and
  alternatives based on cargo features with not(), any() and all() support

Bugfixes

• Improvements to error message reporting to improve clarity and suppress extra noise
• lalrpop_mod!() now handles imports correctly
• Reenable some warnings on user code for custom lexers

v0.21.0

Compare Source

Since the last release, a fair number of the commits have been focused on cleaning
up and improving LALRPOP's documentation. Shout out to Yudai Takada, George
White, and Dinu Blanovschi.

Features

• LALRPOP now throws an error in more cases where it would previously just write
  out an error message and exit.
• lalrpop::process_src is now the recommended function to use in build.rs
  files. Previously the documentation incorrectly suggested that
  lalrpop::process_root looked in ./src instead of .

Bugfixes

• A long-standing bug where LALRPOP would throw a "no entry found for key"
  exception when trying to handle certain grammars has been resolved.
• LALRPOP will stop expanding macros infinitely during build time via a new
  macro_expansion_limit.

Compatibility note

Adding a limit to the number of times that LALRPOP will attempt to expand a
macro is technically a breaking change. However, the default limit of 200
should be more than enough for the grammars we are currently aware of (which
almost always need a limit of less than 5). This limit is customizable via Configuration::set_macro_expansion_limit.

If you have a grammar that uses a significant amount of macro expansion steps,
we would be very interested in a PR that adds it to the test suite.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.22.0
    Updating crates.io index
error: failed to select a version for the requirement `lalrpop-util = "^0.20.0"`
candidate versions found which didn't match: 0.22.0
location searched: crates.io index
required by package `lalrpop v0.20.2`
    ... which satisfies dependency `lalrpop = "^0.20.1"` (locked to 0.20.2) of package `intersection v1.0.0 (/tmp/renovate/repos/github/intersection-project/intersection)`