syscall: bump syscall numbers up

Currently the new popcorn syscall numbers are placed consequetively after
the last, vanilla, defined ones. This causes troubles if userspace is built
against a newer kernel, with new syscalls, and checks for them by calling
and expecting a ENOSYS as a sign that the needed syscall's missing.

Specifically kmod does this with finit_module() - which isn't present in
our kernel, however sys_get_boot_params_addr() has the same syscall number,
and thus kmod's tricked into using finit_module() instead of the (present)
init_module().

Signed-off-by: Veaceslav Falico <vfalico@gmail.com>