fix: issue 1728 when useSuspense is false and default ns

[timheilman]

is custom, in strict mode only, memoization is performed of an unready translation function and is not refreshed after readiness.

The use of the isInitial ref is fundamentally incompatible with strict mode. Substituting ready instead seems to fix #1728 and keep both #1691 and #1718 fixed

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

Checklist (for documentation change)

• only relevant documentation part is changed (make a diff before you submit the PR)
• motivation/reason is provided
• commit message and code follows the Developer's Certification of Origin

[coveralls]

coverage: 97.017% (-0.003%) from 97.02%
when pulling 5b98721 on timheilman:fix/1728-custom-default-ns-useSuspense-false-in-strict-mode-fails-initialization
into d95d697 on i18next:master.

[timheilman]

A review from @medihack would be much appreciated, especially for the shallow routing issue he was familiar with. It's a shame it's so difficult to unit-test StrictMode.

[adrai]

thx, it's included in v14.0.8