fix(lookup): fixed keys with dots

[Matergi]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller
  PRs).
• This PR avoids mixing refactoring changes with feature changes (split into
  two PRs otherwise).
• This PR's title starts is concise and descriptive.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or
  fixes.
• I've updated any docs, .md files, etc… affected by this change.

What

Added support for the character '.' in the translation key

Why

Some translation keys can accurately reflect the translated English sentence, for example: 'Only available for Desktop. On the Mobile App, the display ecc...', so support for all punctuation characters is needed

The 3.9.2 version worked fine with dots.

Info

The lodash 'get' function splits by char '.' and looks for the keys, like dictionary[splitKey[0]][splitKey[1]][...];

// doesn't support this:
{
    "standard": {
        "Only available for Desktop. On the Mobile App, the display etc...": "translation",
    }
}

The problem is when a key contains a '.' because the lodash 'get' function interprets it not as part of the key but as a separator.
So, the solution is to use a reduce function to iterate through all the keys in the path generated by:

i18n/src/helpers/lookup.ts

Lines 34 to 36 in d4a14ca

	scope = getFullScope(i18n, scope, options)
	.split(i18n.defaultSeparator)
	.map((component) => i18n.transformKey(component))

[Matergi]

fix this issue: #59

[mattias-persson]

@fnando can this be merged? Having the same issue...

[suparngp]

@fnando, facing the same issue. Can this be merged?

[fnando]

@Matergi I rebased and added some additional changes required by this on #76. Could you please take a look at that branch and test everything to ensure we're not missing anything?

[fnando]

I'm closing this in favor of #76. Please post new comments there.