Use md5 hash for caching on node v17

[Reptarsrage]

Please check if the PR fulfills these requirements

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

• 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? (You can also link to an open issue here)
#917

What is the new behavior?
Webpack builds will succeed with latest node version 17.0.0 if you set the new "hashType" configuration value to "md5".

Does this PR introduce a breaking change?

• Yes
• No

[Reptarsrage]

Looks like "md4" is now considered "legacy" in OpenSSL 3.0 and is not supported without some tweaking (source, source). This change allows users to specify a supported hash algorithm.

[nicolo-ribaudo]

Would it be a breaking change to just switch to md5 by default?

[JLHwung]

Would it be a breaking change to just switch to md5 by default?

Changing hash algorithm will invalidate current cache. I think offering a hashType is overkill, we can use md5 on Node >= 17 and migrate to md5 in next major.

[Reptarsrage]

@JLHwung I switched the change to conditionally switch to md5 if it detects node v17.0.0 or higher.

[JLHwung]

Thanks!

[nicolo-ribaudo]

Thanks!