feature: dynamic secret/keys via secretOrKeyProvider

[tomsiwik]

PR Checklist

Please check if your PR fulfils 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
[x] 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 behaviour?

There is no way to assign a secret dynamically.
Related to issue number: #26

What is the new behaviour?

With secretOrKeyProvider you can assign a secret or public/private key for each sign/verify request separately.

Does this PR introduce a breaking change?

[ ] Yes
[x] No //changed, see last commit

This PR introduces a breaking change how secretOrPrivateKey is assigned. Before, on the verification step the private Key was used when publicKey was not assigned due to secretOrPrivateKey function. Setting the secret or private/public key is now explicit. The following options set the secret now by priority:

1. secretOrKeyProvider
2. secret
3. publicKey and privateKey

Edit:

secretOrKey was re-added to smoothen out the upgrading process and takes precedence over the listed options above. With a deprecation warning and added tests this should be enough I hope.

Other information

I'm currently in the process of adding tests to this module. However, suggestions, critique or discussions are welcome. My time is quite limited but I'm happy to help and answer questions.

This is my first contribution to open source :) quite exciting tbh.

[tomsiwik]

@kamilmysliwiec hey, small heads up that the PR is ready. I have added a few tests for the changes I made but I'm not used to testing (especially not with nestjs). Hope everything is fine like that. Please let me know if there is anything to improve.

[tomsiwik]

Small note: I re-added secretOrKey with a deprecation warning and tests to make the upgrade smoother between versions. Hope that helps.

[shayded-exe]

I'm currently having to implement a workaround until this is released. It would be awesome if it was merged soon :)

[tomsiwik]

I'm racing against renovate. Will create a new PR with a single commit