Fix: _EnableSelector type (for compatibility, enableSelector does not exist in TypeOptions)

[nemuvski]

Hello,

I have updated to v15.7.0, but I encountered a case where type inference with useTranslation() does not work correctly.

In my project, I am using i18next v25.3.x.
(I am aware that updating to v25.4 would resolve the issue.)

Since enableSelector is not defined in TypeOptions, type inference is failing.

Looking at the peerDependencies, I noticed that "i18next": ">= 23.2.3" is specified.
Considering compatibility, I thought it would be appropriate to handle cases where enableSelector is not present in TypeOptions, so I made this PR.

Thank you for your consideration.

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

[adrai]

@ahrjarrett ok for you?

[coveralls]

coverage: 95.864%. remained the same
when pulling 73a7260 on nemuvski:fix-enableselector-type
into 1d7ad47 on i18next:master.

[ahrjarrett]

Ah, good catch. @adrai yep, makes sense to me

[adrai]

Thank you...
included in v15.7.1