Bump regex from 0.2.2 to 1.6.0 in /journald-cloudwatch

[dependabot]

Bumps regex from 0.2.2 to 1.6.0.

Release notes

Sourced from regex's releases.

1.0.0

This release marks the 1.0 release of regex.

While this release includes some breaking changes, most users of older versions of the regex library should be able to migrate to 1.0 by simply bumping the version number. The important changes are as follows:

• We adopt Rust 1.20 as the new minimum supported version of Rust for regex. We also tentativley adopt a policy that permits bumping the minimum supported version of Rust in minor version releases of regex, but no patch releases. That is, with respect to semver, we do not strictly consider bumping the minimum version of Rust to be a breaking change, but adopt a conservative stance as a compromise.
• Octal syntax in regular expressions has been disabled by default. This permits better error messages that inform users that backreferences aren't available. Octal syntax can be re-enabled via the corresponding option on RegexBuilder.
• (?-u:\B) is no longer allowed in Unicode regexes since it can match at invalid UTF-8 code unit boundaries. (?-u:\b) is still allowed in Unicode regexes.
• The From<regex_syntax::Error> impl has been removed. This formally removes the public dependency on regex-syntax.
• A new feature, use_std, has been added and enabled by default. Disabling the feature will result in a compilation error. In the future, this may permit us to support no_std environments (w/ alloc) in a backwards compatible way.

For more information and discussion, please see 1.0 release tracking issue.

0.2.7

This release includes a ground-up rewrite of the regex-syntax crate, which has been in development for over a year.

New features:

• Error messages for invalid regexes have been greatly improved. You get these automatically; you don't need to do anything. In addition to better formatting, error messages will now explicitly call out the use of look around. When regex 1.0 is released, this will happen for backreferences as well.
• Full support for intersection, difference and symmetric difference of character classes. These can be used via the &&, -- and ~~ binary operators within classes.
• A Unicode Level 1 conformat implementation of \p{..} character classes. Things like \p{scx:Hira}, \p{age:3.2} or \p{Changes_When_Casefolded} now work. All property name and value aliases are supported, and properties are selected via loose matching. e.g., \p{Greek} is the same as \p{G r E e K}.
• A new UNICODE.md document has been added to this repository that

... (truncated)

Changelog

Sourced from regex's changelog.

1.6.0 (2022-07-05)

This release principally includes an upgrade to Unicode 14.

New features:

• [FEATURE #832](rust-lang/regex#832): Clarify that Captures::len includes all groups, not just matching groups.
• [FEATURE #857](rust-lang/regex#857): Add an ExactSizeIterator impl for SubCaptureMatches.
• [FEATURE #861](rust-lang/regex#861): Improve RegexSet documentation examples.
• [FEATURE #877](rust-lang/regex#877): Upgrade to Unicode 14.

Bug fixes:

• [BUG #792](rust-lang/regex#792): Fix error message rendering bug.

1.5.6 (2022-05-20)

This release includes a few bug fixes, including a bug that produced incorrect matches when a non-greedy ? operator was used.

• [BUG #680](rust-lang/regex#680): Fixes a bug where [[:alnum:][:^ascii:]] dropped [:alnum:] from the class.
• [BUG #859](rust-lang/regex#859): Fixes a bug where Hir::is_match_empty returned false for \b.
• [BUG #862](rust-lang/regex#862): Fixes a bug where 'ab??' matches 'ab' instead of 'a' in 'ab'.

1.5.5 (2022-03-08)

This releases fixes a security bug in the regex compiler. This bug permits a vector for a denial-of-service attack in cases where the regex being compiled is untrusted. There are no known problems where the regex is itself trusted, including in cases of untrusted haystacks.

• SECURITY #GHSA-m5pq-gvj9-9vr8: Fixes a bug in the regex compiler where empty sub-expressions subverted the existing mitigations in place to enforce a size limit on compiled regexes. The Rust Security Response WG published an advisory about this: https://groups.google.com/g/rustlang-security-announcements/c/NcNNL1Jq7Yw

1.5.4 (2021-05-06)

... (truncated)

Commits

• fc9ee6a 1.6.0
• 8ddc8ec deps: bump regex-syntax to 0.6.27
• 8c0eccd regex-syntax-0.6.27
• dee5c25 changelog: 1.6.0
• 9ca3099 regex: fix clippy lints up to rust 1.41.1
• de83828 syntax: fix clippy lints up to rust 1.41.1
• b87cd88 syntax: include only the start of the character class on error
• 9d1478c doc: fix typos
• 7d21662 doc: clarify Captures::len includes non-matching captures
• 5e98788 perf: use is_match_at instead of shortest_match_at
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.