Better story for testing with lazy-loaded translations config

[runspired]

Currently for every test you must set the locale and await the fetch and add the translations, would be great to be able to do this more easily.

[CarlosLazarini]

I second this. I'm trying to change my app to work with lazy loading translations and I'd need to change thousands of tests.

[runspired]

I can post our setup later, you can do a global test setup. Not terribly hard, just a guide for it would be good.

[CarlosLazarini]

@runspired that would be great, appreciate it 🙌

[jahrock]

@runspired would be interested in your reference implementation.

In our scenario, we don't use the intl service directly, as we have created a middle layer translation service that interacts with the intl service on it's own.

For this reason, I disabled lazy loading during the execution of our tests in the first step: publicOnly: environment !== 'test',

This eliminates the need to manually load the translations in each test, but the language still needs to be set.

[runspired]

described our setup mostly here #1659 (comment)