types: use unknown to better infer types on nested t functions

[marcalexiei]

While upgrading to v23 we encounter the same issue described in #2011.

The problem seems caused by any usage in defaultValue, interpolation map and dictionary.
Changing them to unknown should make type infer from nested t work properly.

We have tested this patch on our repository and it seems to be working.

Before

After

Without CustomTypeOptions

With CustomTypeOptions

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• run tests npm run test
• tests are included
• commit message and code follows the Developer's Certification of Origin

[coveralls]

coverage: 92.36%. remained the same when pulling b4abeaf on marcalexiei:feature/unexpected-any-on-nested-t-functions into 181dcbd on i18next:master.

[koji--]

I was trying to see if it would work if it was a string type, but it seems that unknown type would be fine:+1:

[AriPerkkio]

Ran into this issue as well in real world application, and verified that by modifying the type $Dictionary in node_modules/i18next/typescript/helpers.d.ts seems to fix the issue - thanks @marcalexiei!

Are there any work-arounds before this PR is merged and released? Any ways how to overwrite those types with Typescript without using NPM package patches?

[pedrodurek]

Seems great to me! Thanks!

[marcalexiei]

HI @adrai, could you please merge and release this PR when you have the chance?

[adrai]

thank you @marcalexiei it's included in v23.5.0