ci: run tests on node v19

[snitin315]

What kind of change does this PR introduce?
CI (also need update deps).

Run tests on node 19 as well.

Did you add tests for your changes?
No need.

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
Nothing

[webpack-bot]

For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

[snitin315]

I believe we need to update jest.

[alexander-akait]

Wierd:

Unable to find JEST_STATE_SYMBOL in Symbol(jest-native-promise), Symbol(jest-native-now), Symbol(jest-native-read-file), Symbol(jest-native-write-file), Symbol(jest-native-exists-file), Symbol($$jest-matchers-object), Symbol(graceful-fs.queue)

I believe we need to update jest.

Yeah, but we still need to run tests on Node.js v10, anyway we try to update jest and install old version of jest for v10

[TheLarkInn]

@snitin315

This is the suspect code:

webpack/test/helpers/createLazyTestEnv.js

Lines 1 to 12 in b7fc4d8

	const STATE_SYM = Object.getOwnPropertySymbols(global).find(
	Symbol("x").description
	? s => s.description === "JEST_STATE_SYMBOL"
	: s => s.toString() === "Symbol(JEST_STATE_SYMBOL)"
	);
	if (!STATE_SYM) {
	throw new Error(
	`Unable to find JEST_STATE_SYMBOL in ${Object.getOwnPropertySymbols(global)
	.map(s => s.toString())
	.join(", ")}`
	);
	}

It appears to break due to any Node version > 16

[alexander-akait]

I will look at this

[alexander-akait]

@SimenB Friendly ping, maybe you can give us some advices, I tried to find why it doesn't work on v18 and no luck, I found jest has require("jest-circus/build/state").getState(), but it looks like return no current state, because currentDescribeBlock.tests is empty. So what is the big different between jest v27 on Node v16 and Node v18? May it be a bug?