[Bug]: OgmaCoreModule cot configured

[jmcdo29]

Bug Report

Currently, if @OgmaLogger() is used in any test the error Error: Expected OgmaCoreModule to be configured by at last one Module but it was not configured within 0ms will appear in the console. While this doesn't fail the test, because it is an UnhandledPromiseRejection it may end up failing in the future.

Input Code

@Injectable()
export class AppService {
  constructor(@OgmaLogger(AppService) private readonly logger: OgmaService) {}

  getHello(): Record<string, string> {
    this.logger.log("Say Hello!");
    return { hello: "world" };
  }
}

describe('AppService', () => {
  let service: AppService;

  beforeEach(async () => {
    const modRef = await Test.createTestingModule({
      providers: [
        AppService,
        {
          provide: 'OGMA_SERVICE:AppService',
          useValue: {
            log: jest.fn(),
          }
        }
      ]
    }).compile();
    service = modRef.get(AppService);
  });

  it('should be defined', () => {
    expect(service).toBeTruthy();
  });
  it('should return { hello: world }', () => {
    expect(service.getHello()).toEqual({ hello: 'world' });
  });
});

Expected behavior

No errors to arise when running unit tests.

Possible Solution

In the OgmaModule's @Module() metadata, imports: [OgmaCoreModule.Deferred] is used. Because of this, and because it is in a decorator, it gets ran immediately, which means the observable there will be fired and possibly end up erroring out. It can probably be removed as the forRoot, forRootAsync, and forFeature all use the imports directly

Environment

@ogma/nestjs-module version: 0.2.0

 
For Tooling issues:
- Node version: 14.5.0  
- Platform:  MacOS 

Others: