Support kernel syscall trace injection in the drmemtrace scheduler

There are various cases where the injected syscall traces (both statically and dynamically) need to be accounted for by the drmemtrace scheduler. E.g., there shouldn't be a context switch in the middle of the syscall trace, syscall traces shouldn't break book-keeping done by the scheduler.

This issue is to explore and handle those cases.