ci: run aarch64 tests native via actuated

[adrianreber]

This brings aarch64 based tests to CRIU GitHub CI setup. The difference to the previous configurations is that now actually all tests (almost) are being run.

The tests on the actuated runners are with following limitations:

• tests using macvlan have to be skipped as that module is not available
• the coredump python script is x86_64 only (register names and other arch specific code)
• the change_mnt_context test fails with

    #    ./change_mnt_context --pidfile=change_mnt_context.pid --outfile=change_mnt_context.out
    #    45: ERR: change_mnt_context.c:23: mount (errno = 22 (Invalid argument))

• the sched_policy00 test fails with

    #    5: ERR: sched_policy00.c:55: Can't set policy (errno = 1 (Operation not permitted))
    #    4: ERR: test.c:320: Test exited unexpectedly with code 255

• in combination with '--remote-lazy-pages' following error occurs:

    #  138: FAIL: maps05.c:84: Data corrupted at page 1639 (errno = 11 (Resource temporarily unavailable))

• the crit test case triggers an out of range error when displaying rss on aarch64 which was fixed based on an old commit from @rst0git

[rst0git]

the sched_policy00 test fails with

Would you be able to check if disabling RT throttling would fix this problem?

sudo sysctl -w kernel.sched_rt_runtime_us=-1

• https://github.com/amazonlinux/amazon-linux-2023/issues/315#issuecomment-1497644537
• https://wiki.linuxfoundation.org/realtime/documentation/technical_basics/sched_rt_throttling