mkconcore run/debug scripts fail when tool paths contain spaces #540

Hi @pradeeban,
I found a path handling issue in generated studies. If a tool path contains spaces (for example, a custom Python/Java path under Program Files on Windows), some commands written by mkconcore.py are not quoted consistently in generated run/debug scripts. Because of that, those scripts can fail even though the tool exists and is configured correctly.
This is especially visible when tool paths are set through concore.tools or environment variables.

Proposed fix:

• consistently quote tool executable paths when writing generated script commands (Windows + POSIX)
• keep behavior unchanged for normal no space paths