Improve textual import running process

[AxelRICHARD]

SysOn relies on SysIDE for the textual import.
Currently, end users have to copy the syside-cli.js file (located inside syson-application module) near the application fat-jar file resulting from the build in order to have the textual import working.

An improvement would be to move the syside-cli.js file inside the syson-sysml-export module and improve the build so end users don't have to copy syside-cli.js near the fat-jar anymore.
The option org.eclipse.syson.syside.path will still be there, allowing end users with execution rights problem to provide a syside-cli.js located in a place where they have the appropriate rights.