Update Rust crate regex to 1.9

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
regex	dependencies	minor	1.8 -> 1.9

---

Release Notes

rust-lang/regex (regex)

v1.9.0

Compare Source

==================
This release marks the end of a years long rewrite of the regex crate
internals. Since this is
such a big release, please report any issues or regressions you find. We would
also love to hear about improvements as well.

In addition to many internal improvements that should hopefully result in
"my regex searches are faster," there have also been a few API additions:

• A new Captures::extract method for quickly accessing the substrings
  that match each capture group in a regex.
• A new inline flag, R, which enables CRLF mode. This makes . match any
  Unicode scalar value except for \r and \n, and also makes (?m:^) and
  (?m:$) match after and before both \r and \n, respectively, but never
  between a \r and \n.
• RegexBuilder::line_terminator was added to further customize the line
  terminator used by (?m:^) and (?m:$) to be any arbitrary byte.
• The std Cargo feature is now actually optional. That is, the regex crate
  can be used without the standard library.
• Because regex 1.9 may make binary size and compile times even worse, a
  new experimental crate called regex-lite has been published. It prioritizes
  binary size and compile times over functionality (like Unicode) and
  performance. It shares no code with the regex crate.

New features:

• FEATURE #​244:
  One can opt into CRLF mode via the R flag.
  e.g., (?mR:$) matches just before \r\n.
• FEATURE #​259:
  Multi-pattern searches with offsets can be done with regex-automata 0.3.
• FEATURE #​476:
  std is now an optional feature. regex may be used with only alloc.
• FEATURE #​644:
  RegexBuilder::line_terminator configures how (?m:^) and (?m:$) behave.
• FEATURE #​675:
  Anchored search APIs are now available in regex-automata 0.3.
• FEATURE #​824:
  Add new Captures::extract method for easier capture group access.
• FEATURE #​961:
  Add regex-lite crate with smaller binary sizes and faster compile times.
• FEATURE #​1022:
  Add TryFrom implementations for the Regex type.

Performance improvements:

• PERF #​68:
  Added a one-pass DFA engine for faster capture group matching.
• PERF #​510:
  Inner literals are now used to accelerate searches, e.g., \w+@​\w+ will scan
  for @.
• PERF #​787,
  PERF #​891:
  Makes literal optimizations apply to regexes of the form \b(foo|bar|quux)\b.

(There are many more performance improvements as well, but not all of them have
specific issues devoted to them.)

Bug fixes:

• BUG #​429:
  Fix matching bugs related to \B and inconsistencies across internal engines.
• BUG #​517:
  Fix matching bug with capture groups.
• BUG #​579:
  Fix matching bug with word boundaries.
• BUG #​779:
  Fix bug where some regexes like (re)+ were not equivalent to (re)(re)*.
• BUG #​850:
  Fix matching bug inconsistency between NFA and DFA engines.
• BUG #​921:
  Fix matching bug where literal extraction got confused by $.
• BUG #​976:
  Add documentation to replacement routines about dealing with fallibility.
• BUG #​1002:
  Use corpus rejection in fuzz testing.

v1.8.4

Compare Source

==================
This is a patch release that fixes a bug where (?-u:\B) was allowed in
Unicode regexes, despite the fact that the current matching engines can report
match offsets between the code units of a single UTF-8 encoded codepoint. That
in turn means that match offsets that split a codepoint could be reported,
which in turn results in panicking when one uses them to slice a &str.

This bug occurred in the transition to regex 1.8 because the underlying
syntactical error that prevented this regex from compiling was intentionally
removed. That's because (?-u:\B) will be permitted in Unicode regexes in
regex 1.9, but the matching engines will guarantee to never report match
offsets that split a codepoint. When the underlying syntactical error was
removed, no code was added to ensure that (?-u:\B) didn't compile in the
regex 1.8 transition release. This release, regex 1.8.4, adds that code
such that Regex::new(r"(?-u:\B)") returns to the regex <1.8 behavior of
not compiling. (A bytes::Regex can still of course compile it.)

Bug fixes:

• BUG #​1006:
  Fix a bug where (?-u:\B) was allowed in Unicode regexes, and in turn could
  lead to match offsets that split a codepoint in &str.

v1.8.3

Compare Source

==================
This is a patch release that fixes a bug where the regex would report a
match at every position even when it shouldn't. This could occur in a very
small subset of regexes, usually an alternation of simple literals that
have particular properties. (See the issue linked below for a more precise
description.)

Bug fixes:

• BUG #​999:
  Fix a bug where a match at every position is erroneously reported.

v1.8.2

Compare Source

==================
This is a patch release that fixes a bug where regex compilation could panic
in debug mode for regexes with large counted repetitions. For example,
a{2147483516}{2147483416}{5} resulted in an integer overflow that wrapped
in release mode but panicking in debug mode. Despite the unintended wrapping
arithmetic in release mode, it didn't cause any other logical bugs since the
errant code was for new analysis that wasn't used yet.

Bug fixes:

• BUG #​995:
  Fix a bug where regex compilation with large counted repetitions could panic.

v1.8.1

Compare Source

==================
This is a patch release that fixes a bug where a regex match could be reported
where none was found. Specifically, the bug occurs when a pattern contains some
literal prefixes that could be extracted and an optional word boundary in the
prefix.

Bug fixes:

• BUG #​981:
  Fix a bug where a word boundary could interact with prefix literal
  optimizations and lead to a false positive match.

---

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 becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.