[BC break] Added implements \Stringable to Translation Value Object

[alongosz]

🎫 Issue	n/a
BC breaks	yes, for 5.0.0 major

Description:

\Ibexa\Contracts\Core\Repository\Values\Translation class has no __toString() method but all two implementations: Plural, and Message - have it. Given we operate on the common abstract contract, it causes static analysis issue:

Error: Cannot cast Ibexa\Contracts\Core\Repository\Values\Translation to string.

This method should be declared on the Translation abstract. The easiest way to solve it is to implement \Stringable on the abstract Translation class, forcing all its children to actually implement public function __toString(): string.

abstract class Translation extends ValueObject implements \Stringable

For QA:

No QA required, regressions are enough.

Documentation:

Should be documented as a breaking change. I'll update proper internal document that will be used when documenting all 5.0 breaks, so for this PR no "doc needed" label.

Checklist:

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

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[adamwojs]

Can we implement \Stringable on \Ibexa\Contracts\Core\Repository\Values\Translation ? It should be covered by php 8.x polyfill package.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud