Feat: Create custom ESLint Rule to avoid lingering modules

[thiagomini]

Description

We need a Rule that enforces closing a TestingModule. When we create a module in tests and don't close it we potentially leak memory and/or database connections.

Acceptance Criteria

The ESLint rule should warn when:

• A Test.createTestingModule() is executed in the beforeEach() hook, but then the module isn’t closed in the afterEach()
• A Test.createTestingModule() is executed in the beforeAll() hook, but isn’t closed in the afterAll() one.
• A Test.createTestingModule() is executed within a test, or it block, but isn't closed.

The ESLint rule should consider valid:

• When a Test.createTestingModule() is executed in the beforeEach() and the module is then closed in the afterEach() hook
• When a Test.createTestingModule() is executed in the beforeAll() and the module is then closed in the afterAll() hook
• When a Test.createTestingModule() is executed, followed by a module.createNestApp(), and then the application is closed in the correct hook