ci: run tests on windows

[timofei-iatsenko]

I have users reporting issues on windows. I configured smoke tests for the application on windows and indeed it's failing.

I searched through issues and there were a bunch of windows issues previously fixed, but tests in the CI were not added. That's why I'm adding them to showcase the problems on windows.

Regarding current issue, example of failing WF is here

https://github.com/timofei-iatsenko/keycloakify-emails/actions/runs/12416203815/job/34664284560

It's failing with:

ReferenceError: require is not defined
    at moduleImport (file:///D:/a/keycloakify-emails/keycloakify-emails/node_modules/.pnpm/jsx-email@2.5.3_patch_hash=lw572etmmjvpxarowkqqptjobm_@jsx-email+plugin-inline@1.0.1_@jsx-ema_3cnz4xvaxhfemvgnnu2s7rzzne/node_modules/jsx-email/src/config.ts:201:6)
    at Object.search (D:\a\keycloakify-emails\keycloakify-emails\node_modules\.pnpm\lilconfig@3.1.2\node_modules\lilconfig\src\index.js:222:23)
    at loadConfig (file:///D:/a/keycloakify-emails/keycloakify-emails/node_modules/.pnpm/jsx-email@2.5.3_patch_hash=lw572etmmjvpxarowkqqptjobm_@jsx-email+plugin-inline@1.0.1_@jsx-ema_3cnz4xvaxhfemvgnnu2s7rzzne/node_modules/jsx-email/src/config.ts:219:14)
    at render (file:///D:/a/keycloakify-emails/keycloakify-emails/node_modules/.pnpm/jsx-email@2.5.3_patch_hash=lw572etmmjvpxarowkqqptjobm_@jsx-email+plugin-inline@1.0.1_@jsx-ema_3cnz4xvaxhfemvgnnu2s7rzzne/node_modules/jsx-email/src/renderer/render.ts:46:16)
    at Object.getTemplate (file:///D:/a/keycloakify-emails/keycloakify-emails/example/emails/templates/email-test.tsx:35:10)
    at renderTemplate (file:///D:/a/keycloakify-emails/keycloakify-emails/dist/index.mjs:68:20)
    at renderThemeVariant (file:///D:/a/keycloakify-emails/keycloakify-emails/dist/index.mjs:162:5)

I dug into jsx-email sourcecode, it seems problem is here:

jsx-email/packages/jsx-email/src/config.ts

Lines 194 to 210 in 29851f2

	const moduleImport = async (id: string) => {
	try {
	const mod = await import(id);
	return mod;
	} catch (e) {
	try {
	return require(id);
	} catch (error) {
	if (
	(error as any).code === 'ERR_REQUIRE_ESM' ||
	(error instanceof SyntaxError &&
	error.toString().includes('Cannot use import statement outside a module'))
	) {
	throw e;
	}
	throw error;
	}

The first try catch is actually hiding the original issue. I patched the sourcecode and added another throw to reveal the original error message and got this one:

Error: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'd:'

Worth mentioning that similar issue was not reproducible in my test suite in Vite, i suppose it's because vite is doing some pre-processing for files and nodejs receives not original import.

Component / Package Name:

This PR contains:

• bugfix
• feature
• refactor
• documentation
• other

Are tests included?

• yes (bugfixes and features will not be merged without tests)
• no

Breaking Changes?

• yes (breaking changes will not be merged unless absolutely necessary)
• no

If yes, please include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.

List any relevant issue numbers:

Description