Update friendsofphp/php-cs-fixer dependency to PHP 8 Compatible version

[sivaschenko]

Description (*)

Update friendsofphp/php-cs-fixer dependency version to "~2.18.0"

Expected behavior (*)

Benefits

Additional information

[m2-assistant]

Hi @sivaschenko. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[hostep]

Version 2.18.0 was released a couple of days ago, does it make sense to directly move to that version?

It contains one more fix needed for php 8 I think?

[sivaschenko]

@hostep yes, thank you! Updated. cc @konarshankar07

[magento-engcom-team]

Hi @sivaschenko, @konarshankar07.

Thank you for your report and collaboration!

The related internal Jira ticket MC-39653 was closed as Complete.

The fix will be available with the upcoming 2.4.3 release.