fix: use sha256 instead of md5 to support openssl 3.0 and on

[jmcdo29]

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?

OpenSSL 3.0+ has an issue with md5

Issue Number: #2094

What is the new behavior?

Use sha256 instead of md5

Does this PR introduce a breaking change?

• Yes
• No

By some small technicality, this could be a breaking change in that the old keys will no longer be valid. That should be a rather small margin of users and for such a short period of time (presumably) that it shouldn't be an issue.

Other information

[jmcdo29]

@Xaala let me know what you think. Should be a pretty straightforward change

[Xaala]

Exactly what I had in mind @jmcdo29 thanks for the quick turnaround.

[Xaala]

Confirmed to have fixed issues with upgrading to OpenSSL 3.0 and beyond, thanks again for the quick turn around, appreciate it.