add keyPath support for react-i18n-next

[vovsemenv]

Allow keyPath support for react-i18n-next useTranslation hook

closes #719

[vovsemenv]

@terales can you check it?

[soapwong703]

Thanks for the help, I defenitely need this feature! However I pulled your PR and are having two problems:

1. keyPrefix will go before the namespace ('component.common.title')
2. the first keyPrefix in the file will override the later keyPrefix ('component.common.submit')

The correct key should be 'common.component.title' and 'common.action.page'.

Would you kindly fix it?

[vovsemenv]

@soapwong703
i can fix this part (in my setup i use only default namespace)

1. keyPrefix will go before the namespace ('component.common.title')

in my realization extension can work only be configured in file scope so you shoud have only one component in one file, but you can help me to fix it

the first keyPrefix in the file will override the later keyPrefix ('component.common.submit')

[JulesLecuir]

Hi @vovsemenv how is this PR going ? Looking forward to it ! :)

[vovsemenv]

i guess it waiting for @terales review

[JulesLecuir]

oops, little typo here ! ;)

[JulesLecuir]

I guess the key separator should be dynamic, as it can be configured in the i18nally configuration

[terales]

Can we add a test here (at least as a small e2e test to the https://github.com/lokalise/i18n-ally/tree/main/examples/by-frameworks)?