Upgrade locked version of phpunit

[mvorisek]

Questions	Answers
Branch?	develop
Description?	Upgrade locked phpunit and related deps to the latest version.
Type?	improvement
Category?	TE
BC breaks?	no
Deprecations?	no
How to test?	CI must pass
Fixed ticket?	n/a
Related PRs	n/a
Sponsor company	MAHALUX

[mvorisek]

001 Scenario: Delete all products from order then add product in the empty order # Features/Scenario/Order/order_from_bo.feature:693
      And order "bo_order1" should have following tax details:                   # Features/Scenario/Order/order_from_bo.feature:734
        Invalid order tax field unit_amount, expected 0.9 instead of 0.9
        Failed asserting that 0.8999999999999999 matches expected 0.9.

002 Scenario: I use and address without taxes (no order_detail_tax created), then I change to a country with taxes all is correctly computed # Features/Scenario/Order/order_shipping.feature:728
      And the first invoice from order "bo_order1" should have following shipping tax details:                                               # Features/Scenario/Order/order_shipping.feature:836
        Invalid order tax field total_amount, expected 0.36 instead of 0.36
        Failed asserting that 0.3600000000000003 matches expected 0.36.

003 Scenario: In rounding per item mode, I use an address without taxes (no order_detail_tax created), then I change to a country with taxes all is correctly computed # Features/Scenario/Order/order_shipping.feature:871
      And the first invoice from order "bo_order1" should have following shipping tax details:                                                                         # Features/Scenario/Order/order_shipping.feature:980
        Invalid order tax field total_amount, expected 0.36 instead of 0.36
        Failed asserting that 0.3600000000000003 matches expected 0.36.

1189 scenarios (1186 passed, 3 failed)

feature: https://github.com/PrestaShop/PrestaShop/blob/bdee2c642/tests/Integration/Behaviour/Features/Scenario/Order/order_from_bo.feature#L736

see sebastianbergmann/comparator#102 for the reason, the number needs to be probably rounded somewhere as tweaking the test might not be desired

What is the wanted fix?

[mvorisek]

closing as no reaction