Improve specification of lorem module and definitions

[ST-DDT]

Languages that use latin characters should use the latin lorem text (e.g. copy it from en).
We will create a separate PR that will document this behavior of the lorem feature in the definitions and module.
After the change of definitions we should create another PR that actually changes the locale data to comply with the new spec and additional care should be taken regarding tree shakeability if the locale data are imported from other locales.

Especially the later part should be done by the team to ensure there are no side effects.

Originally posted by @ST-DDT in #2824 (comment)

[ST-DDT]

Suggestion by @matthewmayer

If it is identical to en could we not just have words.ts be like this to avoid duplication:

import words from '../../en/lorem/words';
export default words;

[xDivisionByZerox]

I'll create a PR for the documentation part. Unless you are already working on it.

[ST-DDT]

#2907 (comment)

This raises my impression that lorem should be strictly Latin only and we should probably add gibberishSentence/Paragraph/Text methods to the word module instead.

[xDivisionByZerox]

Honestly, as long as we have a clear definition I'm fine with it. It's not like we can't change it in the future, if required.

[matthewmayer]

If we do decide to to keep lorem non-Latin languages we should definitely allow for languages that don't have a space as a word seperator (e.g. Chinese, Thai). For example here you'd probably want to use a definition like faker.definitions.lorem.word_seperator instead of a hardcoded ' '.