Set explicit doctrine/lexer version dependency

[zanardigit]

Bolt v5 is not compatible with doctrine/lexer v3 which introduces a breaking change: the token is now an object of class Doctrine\Common\Lexer\Token and not an array anymore. A normal composer update in a Bolt CMS based project may now generate an error: Cannot use object of type Doctrine\Common\Lexer\Token as array. The error goes away if doctrine/lexer v2 is explicitly required.

On a separate PR I will propose an actual fix. This is about setting the dependency in Bolt CMS own composer.json.

[bobvandevijver]

😞 I wanted to merge this, but one of the dev dependencies (coduo/php-matcher) requries doctrine/lexer v1. Would you be open to look into this?

(note that I rebased the branch to be able to run the updated actions)

[zanardigit]

Let's see. I am already using the modified version successfully in PROD, as that conflict is on a DEV requirement, so I'd rather not revert back to doctrine/lexer v1. We could bump php-matcher to version 6 but is only compatible with PHP 8.1+, would that be ok?

[bobvandevijver]

That depends on the outcome of this vote: #3538. It has been opened just yesterday (so I want to give it some time), but I expect we will be dropping 8.0 and older soon.

[bobvandevijver]

This has been superseded by #3558, which has been merged.