feat(linter): add rule for no assignment in function parameters

[chrisopperwall-qz]

📌 What Does This PR Do?

This PR adds a no_assign_in_argument rule to lint similar use cases to no_assign_in_condition, where an assignment expression within a function call argument is not allowed.

🔍 Context & Motivation

This rule would be helpful to warn or error in cases where it's clearer to assign a variable in its own statement, and then use that variable in the function call, instead of nesting the assignment expression in the function call argument.

🛠️ Summary of Changes

• Feature: Added correctness/no_assign_in_argument rule.

📂 Affected Areas

• Linter
• Formatter
• CLI
• Composer Plugin
• Dependencies
• Documentation
• Other (please specify):

🔗 Related Issues or PRs

📝 Notes for Reviewers

The inspiration for this change is this hhast-lint rule which discourages assignment expressions in function call arguments because

• users may assume that new variable isn't available in the current scope/context.
• it looks like keyword args, which exist now via a different syntax in PHP 8.

https://github.com/hhvm/hhast/blob/v3.27.4/src/Linters/NoBasicAssignmentFunctionParameterLinter.php

I'm a little new to rust, so I mostly followed the example of correctness/no_assign_in_condition, so if there's any feedback I'm happy to make changes!

[azjezz]

Hi @chrisopperwall-qz !

Thank you for the PR!

Just few notes :)

[azjezz]

You can use just fix to fix clippy and/or formatting that are causing build failure now

[chrisopperwall-qz]

Thanks, @azjezz! I'll address those comments soon

[azjezz]

Thank you @chrisopperwall-qz !