fix: Fix crash when setting logger to false

[ostkrok]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/terminus/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

When setting up the terminus module with logging disabled according to the documentation:

TerminusModule.forRoot({ logger: false })

the application will crash, with the following error:

Error starting application TypeError: this.logger.setContext is not a function
    at new HealthCheckService (/app/node_modules/@nestjs/terminus/dist/health-check/health-check.service.js:39:21)

This is caused by incorrect typing of the logger injected into HealthCheckService. It's typed to be a ConsoleLogger, which is why it looks safe to call setContext.

This is not true when passing {logger: false}, and probably not when using a customer logger either.

What is the new behavior?

Setting up the terminus module with logging disabled no longer crashes the app :)

If a ConsoleLogger is provided, we still call setContext in order to preserve the old behavior. I guess we could consider calling setContext as long as it exists on the logger object instead?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[BrunnerLivio]

Oups that fell under my radar, thanks for noticing!
Released with v9.2.1 🎉