feat(@nestjs/passport): segregate authenticate opts from module opts

[rodrigo-speller]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/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?

Issue Number: #947

• AuthGuard's constructor receives, by injection, the AuthModuleOptions object, that's responsible to configure the module of this library;
• AuthGuard.getAuthenticateOptions returns an object that matches the interface IAuthModuleOptions;
• AuthGuard.canActivate obtain the options from getAuthenticateOptions and merges it with the injected options of the AuthGuard instance;
• AuthGuard.canActivate pass the merged options to passport.authenticate.

What is the new behavior?

• AuthGuard's constructor receives, by injection, the AuthModuleOptions object, that's responsible to configure the module of this library within authenticateOptions property to generate the options parameter to call passport.authenticate function.
• AuthGuard.getAuthenticateOptions returns an object that matches the passport.AuthenticateOptions interface;
• AuthGuard.canActivate obtain the options from getAuthenticateOptions and merges it with the authenticateOptions from the injected options of the AuthGuard instance;
• AuthGuard.canActivate pass the merged options to passport.authenticate.

Does this PR introduce a breaking change?

• Yes
• No

If the user defines some authenticate option when registering the authentication module by the module options, it must be defined inside authenticateOptions property.

// before:
PassportModule.register({
  defaultStrategy: 'local',
  session: true,
  failureRedirect: '/access-denied',
  successRedirect: '/home'
})

// after:
PassportModule.register({
  defaultStrategy: 'local',
  session: true,
  authenticateOptions: {
    failureRedirect: '/access-denied',
    successRedirect: '/home'
  }
})

Other information

No more information.

[kamilmysliwiec]

This introduces a major breaking change. Could we, instead of adding another nested configuration object, just strip AuthModule-specific props?