Windows run.bat passes run(cmat.m) without quotes, so MATLAB and Octave nodes don't start #636

On a windows build, MATLAB and Octave nodes don't start. They get run(cmat.m) instead of run('cmat.m'), so MATLAB/Octave looks for a variable called cmat.

mkconcore.py (lines 1284-1288) puts q_source inside --eval "run(...)" / -batch "run(...)", and q_source already has double quotes. So run.bat gets nested double quotes:

start /B /D "CZ" "matlab" -batch "run("cmat.m")" >"CZ"\concoreout.txt

The inner quotes just close and reopen the outer string, so the argument ends up as run(cmat.m). I swapped matlab for a small python script that prints its argv and got ['-batch', 'run(cmat.m)']. Same thing with concore.octave present, and in debug.bat. Before 991373c it used run('cmat.m'). The posix scripts still do that and work fine.

Steps: python mkconcore.py testsou/testMM.graphml testsou out windows, then check out/run.bat.

Tested on dev at 8f3e444, Windows 11, Python 3.12.10