chore: upgrade PHPStan and Rector to v2

[martin-georgiev]

Summary by CodeRabbit

• Chores

  • Updated development dependencies and build configurations to leverage new major versions.
  • Adjusted static analysis settings for improved tool accuracy.

• Refactor

  • Refined type handling and validation logic to enhance internal data transformation consistency.
  • Streamlined input verification processes to improve error management.

• Tests

  • Enhanced test annotations and configuration clarity to support more robust testing.
  • Added type annotations for clarity in test case properties.

[coderabbitai]

Walkthrough

The pull request updates PHPStan configurations by adding new ignore error messages and a parameter, bumps development dependency versions in composer.json, refines type handling in the Doctrine DBAL types and utility classes, and adds PHPStan ignore annotations in Doctrine ORM Query functions and tests. The changes adjust internal validation and error handling without altering the public API.

Changes

File(s)	Change Summary
ci/phpstan/baselines/lexer-constants.neon ci/phpstan/config.neon	Updated PHPStan configurations: added two new ignore error messages for type mismatches and a new parameter treatPhpDocTypesAsCertain: false.
composer.json	Updated dependency version constraints for development packages, including PHPStan, Rector, and related tools.
src/.../DBAL/Types/BaseType.php src/.../DBAL/Types/TextArray.php	In DBAL types: changed constant TYPE_NAME from null to '' with updated validation logic, and removed an array type check in transformToPostgresTextArray.
src/.../ORM/Query/AST/Functions/BaseFunction.php src/.../ORM/Query/AST/Functions/BaseVariadicFunction.php	Added // @phpstan-ignore-next-line annotations in parser node methods to suppress static analysis warnings.
src/.../Utils/DataStructure.php tests/.../TestCase.php	Modified type handling in array transformation methods and error assertions, and introduced a new FIXTURES_DIRECTORY property with appropriate PHPDoc and ignore comments in tests.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant DataStructure

    Caller->>DataStructure: transformPHPArrayToPostgresTextArray(text)
    DataStructure->>DataStructure: Evaluate if text is numeric or a digit
    alt Text is numeric
        DataStructure-->>Caller: Return numeric text as-is
    else Text is non-numeric
        DataStructure->>DataStructure: Assert text is a valid string
        DataStructure->>DataStructure: Format text using sprintf
        DataStructure-->>Caller: Return formatted string
    end

Loading

Poem

I'm a bunny in the code grove, so light,
Hopping through changes with a joyful byte.
I nibble on baselines and leap past error lines,
Upgraded dependencies make my heart shine.
Cheering each update with a twitch and a smile,
Coding in springtime, hopping every mile!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 04d001f and 1d5ba2f.

📒 Files selected for processing (1)

• tests/MartinGeorgiev/Doctrine/ORM/Query/AST/Functions/TestCase.php (3 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• tests/MartinGeorgiev/Doctrine/ORM/Query/AST/Functions/TestCase.php

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coveralls]

coverage: 95.989% (+0.4%) from 95.578%
when pulling 04d001f on upgrade-rector-and-phpstan
into d3c5b4b on main.