QML always runs in interpreted mode if profiler is attached

As the QV4DebugService does QV4::ExecutionEngine::enableDebugger() any activation of a debug server will put V4 into interpreted mode, even if only the profiler will be used.

The debugger needs the engine to run in interpreted mode and at least in non-blocking connect mode we don't know if a debugger client shows up at some point during the execution. The engine needs to decide on interpreted or JIT mode when it starts, though.

To fix this, we should tell the debug server in advance which services to load. This can be done with an extension to the -qmljsdebugger command line parameter.

Another way to work around this (now that the services are in separate plugins) is to delete plugins with unwanted services.