Fix checkbox remote running memory stress test (Bugfix) (#1167)
Fix checkbox remote running memory stress test
Once a sub process of checkbox-ng service got killed by OOM killer, the
service will be stopped, because of `DefaultOOMPolicy=stop`, and the memory
stress test will be marked as crashed, or the whole test plan will start
over after the service restarts.
> systemd[1]: checkbox-ng.service: A process of this unit has been killed by the OOM killer.
> kernel: oom_reaper: reaped process 908499 (stress-ng-stack), now anon-rss:15720kB, file-rss:704kB, shmem-rss:0kB
> systemd[1]: checkbox-ng.service: State 'final-sigterm' timed out. Killing.
> systemd[1]: checkbox-ng.service: Killing process 908487 (stress-ng) with signal SIGKILL.
> systemd[1]: checkbox-ng.service: Killing process 908488 (stress-ng-stack) with signal SIGKILL.
> systemd[1]: checkbox-ng.service: Killing process 908489 (stress-ng-stack) with signal SIGKILL.
This commit explicitly set `OOMPolicy=continue` so the service will be
able to remain alive, and checkbox remote could finish the memory stress
test.
Created launchers for 24.04. Removing versioned launchers going forward and will deprecate older version launchers in the future (e.g. certify-22.04 style launchers will be deprecated in favor of a single version agnostic launcher called certify-ubuntu-server SERVCERT-1538