🐛 CLI: Add windows support to import:workflow --separate

[that-one-tom]

This PR addresses a bug reported in the community. The CLI command n8n import:workflow --separate would fail on Windows because the fast-glob package requires forward-slashes for patterns (while Windows uses backslashes in paths).

This PR introduces a quick check for process.platform === 'win32' and converts backslashes accordingly if true.

It also removes potentially trailing slashes from the path since one will be appended as part of the pattern (I only did this because the linter complained about the old format).

Tested this on Windows 11 using:

.\packages\cli\bin\n8n import:workflow --separate --input=C:\Users\Tom\Desktop\test
.\packages\cli\bin\n8n import:workflow --separate --input=C:\Users\Tom\Desktop\test\

Workflows were imported in both cases. Also tested this on Ubuntu 20.04 using:

./packages/cli/bin/n8n import:workflow --separate --input=/mnt/c/Users/Tom/Desktop/test
./packages/cli/bin/n8n import:workflow --separate --input=/mnt/c/Users/Tom/Desktop/test/

Again workflows were imported in both cases.

[janober]

Thanks a lot. Got merged.

[janober]

Got released with n8n@0.150.0