fix: remove i18nOptions from I18nContext class

[lamngockhuong]

Description

The root cause stems from this pull request:
#653

We cannot access the i18nOptions passed from the constructor within the static function I18nContext.current. And when an error occurs in any middleware, the I18nContext will not be initialized, causing this.storage.getStore() to return undefined.

Steps to reproduce this issue:

I use i18n in a GlobalExceptionFilter class:

@Catch()
export class GlobalExceptionFilter implements ExceptionFilter {
private i18n: I18nContext<I18nTranslations>;
catch(exception: any, host: ArgumentsHost): void {
    const { httpAdapter } = this.httpAdapterHost;
    const ctx = host.switchToHttp();
    this.i18n = I18nContext.current<I18nTranslations>(host);
    ...
}

Trigger an error in a different middleware:

The error occurs here: I18nContext.current(host);

Linked Issues

Additional context

[coveralls]

coverage: 90.829% (-0.008%) from 90.837%
when pulling d852410 on lamngockhuong:fix.cannot-access-i18n-options-from-i18n-obj
into ac6e4f9 on toonvanstrijp:main.

[lamngockhuong]

@rubiin Please review this PR when you have spare time
Thanks