a potential bug on resolving provider's token - mismatching logic from nestjs core and this package

[micalevisk]

here we have the following:

nestjs-spelunker/src/exploration.module.ts

Lines 143 to 147 in 4c0dfac

	private static tokenIsOptionalToken(
	token: InjectionToken | OptionalFactoryDependency,
	): token is OptionalFactoryDependency {
	return !!(token as any)['token'];
	}

but at nestjs side, I found 2 places where x is OptionalFactoryDependency is being used:

both of them aren't equal to the logic that nestjs-spelunker has. I wonder if this is expected