IBX-1516: Enforced strict comparison between Limitation & Location path strings

[Steveb-p]

Question	Answer
JIRA issue	IBX-1516
Type	bug
Target Ibexa version	v3.3
BC breaks	yes - ❗ it might cause previously valid values to be rejected ❗

Needs discussion

There is a mismatch between validation in Criterion and Limitation.

Criterion uses regex to check that Subtree Limitation is valid.
Subtree Limitation does not validate using this regex and "only" checks that Location path string and Limitation path string use the same beginning.

Early solution presented here ensures that values passed to Limition as path string is the same as the one present in Location (which ends with a trailing slash).

❗ However, because I'm not certain if they should be always exactly equal, I'm marking this as a BC break until discussed.

Checklist:

• Provided PR description.
• Tested the solution manually.
• Provided automated test coverage.
• Checked that target branch is set correctly (master for features, the oldest supported for bugs).
• Ran PHP CS Fixer for new PHP code (use $ composer fix-cs).
• Asked for a review (ping @ezsystems/engineering-team).

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication