chore: run tests on node 17.x in CI

[anshumanv]

• This is a bugfix
• This is a feature
• This is a code refactor
• This is a test update
• This is a docs update
• This is a metadata update

For Bugs and Features; did you add new tests?

NA

Motivation / Use-Case

Node 17 is out so testing running dev-server tests in CI

Breaking Changes

Shouldn't

Additional Info

[anshumanv]

need some tweaks webpack/webpack#14532 will update tomorrow

[codecov]

Codecov Report

Merging #3965 (51b59f9) into master (270da15) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3965   +/-   ##
=======================================
  Coverage   92.62%   92.62%           
=======================================
  Files          14       14           
  Lines        1410     1410           
  Branches      519      519           
=======================================
  Hits         1306     1306           
  Misses         96       96           
  Partials        8        8           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 270da15...51b59f9. Read the comment docs.

[rishabh3112]

We should also add a TODO here so as to remove workaround once resolved on webpack core.

EDIT:
Looks like node v17 and webpack 4 tests are stuck on ubuntu and macos.

[anshumanv]

Not sure why they're stuck maybe we need to skip node 17, webpack 4 combination 🤔

[rishabh3112]

Not sure why they're stuck

Same hashing algorithm issue 😞, check logs.

[alexander-akait]

webpack v4 should not be run on node v17

[anshumanv]

Yep let's skip the combination

[anshumanv]

Seems like node 17 is stuck again 😞

[alexander-akait]

Please move it to separate file helper file and name hashFunction: getHashFunction()

[anshumanv]

Got it