IBX-12594: Bumped ibexa/jms-translation-bundle to ^3.0

[ViniTou]

Why

ibexa/jms-translation-bundle 3.0.0 is the Symfony 8 compatible major. Symfony 8.0 removed the XML DI configuration format that the bundle relied on, so the 2.x line cannot boot on Symfony 8 at all — this bump is a prerequisite for the wider Symfony 8 upgrade (IBX-12046).

3.0.0 also drops the replace: {"jms/translation-bundle": "..."} entry, which is why the sibling PRs in admin-ui, user and taxonomy switch to requiring the fork by name. This repo already required it by name, so only the constraint changes here.

Merge order

This PR merges first in the IBX-12594 set.

ibexa/core 6.0.x-dev still requires ibexa/jms-translation-bundle ^2.6.1, and this repo has ibexa/core in require-dev — so each side needs the other at ^3.0 before its own CI can resolve. CI here is red until this merges; that is the cycle, not a defect. It was proven green with ibexa/core temporarily pinned to its IBX-12594 branch (pin since dropped):

✅ https://github.com/ibexa/test-core/actions/runs/35600826505 — resolved ibexa/core dev-ibx-12594-jms-translation-bundle-3 + ibexa/jms-translation-bundle 3.0.0, all jobs green.

Once this merges, ibexa/core#829 resolves on its own and the rest follow:

1. IBX-12594: Bumped ibexa/jms-translation-bundle to ^3.0 #50 (this PR)
2. IBX-12594: Bumped ibexa/jms-translation-bundle to ^3.0 core#829
3. IBX-12594: Required ibexa/jms-translation-bundle ^3.0 admin-ui#2092, https://github.com/ibexa/taxonomy/pull/453, IBX-12594: Required ibexa/jms-translation-bundle ^3.0 user#148

Risk

The bundle's container shape is unchanged across 2.x → 3.0: service ids, aliases, tags and visibility flags were verified byte-for-byte identical, and the parent:/tag/decorates extension points this repo relies on resolve identically. No service definitions in this repo need to change.

[Steveb-p]

Add dependencies.json to prove that it will work with the right set of dependencies :)