fix(lazy): make client use translations loaded on the server

[rchl]

Instead of client importing and processing messages (translations)
itself on load, pass already loaded messages from the server through
"nuxtState". This will in most cases allow avoiding triggering an extra
network request to fetch lang file for the given locale.

Slight behavior change: The client will no longer import the lang file
itself for the initially used locale. That means that if the lang file
has exported a function, it will only be called on the server and not on
the client. This matches behavior of "asyncData" and I think it makes
more sense in general.

Resolves #486
Resolves #663

[divine]

New release as well?

[rchl]

Published in v6.13.3

[tvld]

Great ))....
Q: is this a breaking change for clients that load the language module proactively at present ?

[rchl]

What exact configuration do you have in mind?
(This will only affect users that use lazy: true)

[tvld]

We use lazy=true but, and I just checked, it seems not in the projects were we load the files ourselves so to work around the issue... So my question was premature; sorry)).
We will rewrite one of the projects with v6.13.3 and will come back if any questions remain on that front )))
Thanks again ))

[yakovyarmo]

for me it still doesn't work since process.server is undefined