build(deps): bump composer/pcre from 3.2.0 to 3.3.2

[dependabot]

Bumps composer/pcre from 3.2.0 to 3.3.2.

Release notes

Sourced from composer/pcre's releases.

3.3.2

What's Changed

• Allow PHPStan 2 by @​SchmidtClaudia in composer/pcre#40

Full Changelog: composer/pcre@3.3.1...3.3.2

3.3.1

What's Changed

• Fix null-removal on nested captured-arrays by @​staabm in composer/pcre#37
• Fix PHPStan extension for matchAllStrictGroups by @​staabm in composer/pcre#38

Full Changelog: composer/pcre@3.3.0...3.3.1

3.3.0

What's Changed

• Support matchAll* variants in PHPStan extensions by @​staabm in composer/pcre#32
• Enable PHPStan Extensions outside of bleeding edge by @​staabm in composer/pcre#31
• Add PHPStan type extension for the replaceCallback callable by @​Seldaek in composer/pcre#33

Full Changelog: composer/pcre@3.2.0...3.3.0

Commits

• b2bed47 Fix phpstan build
• 5c4fc70 Merge branch '2.x'
• ebb81df Allow PHPStan 2.x
• 2227127 Fix type error
• bfa9e76 Update tests for latest phpstan
• c98c498 Update tests for latest phpstan
• 0c1da10 Fix type error
• 63aaeac Merge branch '2.x'
• 26859a8 Fix PHPStan extension for matchAllStrictGroups (#38)
• 7cafee3 Merge branch '2.x'
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The PR updates composer/pcre from 3.2.0 to 3.3.2 in the composer.lock file. Codacy results are up to standards, and no new quality or security issues were detected.

There is a notable discrepancy: the intent analysis specifies that PHPStan version constraints should be updated to allow ^2.0 and that conflict rules should be adjusted. However, the file list only contains composer.lock. The necessary changes to composer.json appear to be missing, which prevents the PR from fully meeting its objectives.

About this PR

• The changes appear incomplete. While composer.lock was updated, the acceptance criteria require updating composer.json to allow PHPStan ^2.0 and to adjust conflict rules for compatibility with library extensions. Please ensure composer.json is updated accordingly.

Test suggestions

• Verify that regular expression matching and replacement logic in the application remains functional with composer/pcre 3.3.2.
• Run static analysis with PHPStan to ensure the updated library extensions and version constraints do not introduce errors.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that regular expression matching and replacement logic in the application remains functional with composer/pcre 3.3.2.
2. Run static analysis with PHPStan to ensure the updated library extensions and version constraints do not introduce errors.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}