fix: make types stricter

[UndefinedBehaviour]

A solution to #1835.
Makes types stricter so that you can't create loggers with unknown options

pino({
    name: 'logger'
    hello: 'world'
});

[UndefinedBehaviour]

The basic idea is to make LoggerOptions a generic type.

const logger = pino({
    name: 'logger',
    level: 'warn',
    customLevels: {
        myLevel: 25
    }
});

This way, given a call such as this one, tsc is still able to infer the type of customLevels (so that we can call logger.myLevel('blabla')) but the type of the options object itself is no longer inferred so if we mistype the name of an option (or if we use an option tht simply doesn't exist), tsc is able to notify us.

[mcollina]

lgtm

[mcollina]

I'm sorry but I'll need to rever this as it breaks Fastify types badly and I don't have time to fix them right now.

[mcollina]

Can you open a fresh PR again that does not break Fastify types, or provide a matching PR to Fastify?

[UndefinedBehaviour]

reopened as #1858