Implement #canTranslate in GlobalTranslatorImpl and call #canTranslate of its sources

[ivi-kiwi]

Similar to the other methods in the GlobalTranslator, it simply iterates through the sources and checks whether a translation is possible there.

The reason for the proposed change is that if you add a source to the GlobalTranslator which overwrites #canTranslate, the logic in there is not taken into account.

In my individual case, this is necessary because I have my own implementations of TranslatableComponent in my project, to which my Translator only reacts if the instance passed to #translate is of the type of my own implementation and therefore my Translator is no longer addressed at all.

[kezz]

See build failures and suggestion.

For reference, although this PR is a good change, your use case of having your own implementation of TranslatableComponent is entirely unsupported and will break in the upcoming Adventure 5.0 release. I would suggest removing your use case for that or migrating to virtual components instead.

[ivi-kiwi]

For reference, although this PR is a good change, your use case of having your own implementation of TranslatableComponent is entirely unsupported and will break in the upcoming Adventure 5.0 release. I would suggest removing your use case for that or migrating to virtual components instead.

Oh, then I'll look into finding a better solution for my case. But it was a handy solution, and it worked very well until the change. 😅