Add supported range of jackalope packages to composer.json

[alexander-schranz]

Problem the latest version of 2.x PHPCR Bundle also installs the jackalope 2.0 packages:

  - Locking doctrine/phpcr-bundle (2.5.0)
  - Locking jackalope/jackalope (2.0.0)
  - Locking jackalope/jackalope-doctrine-dbal (2.0.1)

https://github.com/sulu/SuluHeadlessBundle/actions/runs/9760192331/job/26938459924?pr=139

But this ends on PHP 8.0 and 8.1 with:

PHP Fatal error: Declaration of Doctrine\Bundle\PHPCRBundle\OptionalCommand\Jackalope\InitDoctrineDbalCommand::configure() must be compatible with Jackalope\Tools\Console\Command\InitDoctrineDbalCommand::configure(): void in /home/runner/work/SuluHeadlessBundle/SuluHeadlessBundle/vendor/doctrine/phpcr-bundle/src/OptionalCommand/Jackalope/InitDoctrineDbalCommand.php on line 19

As the return types are correctly only added on the PHPCR 3.0 branch to avoid bc breaks. See #382.

Still the Sulu Bundles will require to atleast set the new version as min requirement else it could happen that 2.5.0 instead of 2.5.1 (including this PR changes) will be installed.

[alexander-schranz]

We may can backport this directly to Sulu: sulu/sulu#7501 currently why PHPCRBundle is downgraded is because Sulu 2.5 requires Dantlech PHPCR Migration bundle and only 2.6 the new one.

[dbu]

thanks for the report! yeah, dependency management is tricky... (and we should have made those commands not extend but wrap the base commands, i guess. inheritance is prone to these kind of problems, decorating would have avoided the problem).

i agree with the change. why do you mark it as draft, anything left to do? (actually, it would be great if you can add a changelog entry explaining what the problem is)

i will look at the 8.1 build failure separately, that is not related to the jackalope issue.

[dbu]

at least the composer.json of the doctrine bundle suggest section indeed recommends to require ^1.3 of jackalope, so if people followed the suggestion they are safe.

[dbu]

i fixed the build in #405 (which indicates we lack tests that would see the conflict with the commands...)

can you please rebase and add to the changelog entry i created?

[alexander-schranz]

we need to increase this range when merging this back to 3.x

[dbu]

thanks