clh: Disable the `seccomp` option temporarily

[likebreath]

Description of problem

We noticed the seccomp option in cloud-hypervisor can introduce periodic failures in Kata's CI since the debug work on VmInfoGet failure (issue #2864). We continued to see instability of some CLH CI jobs, espcially the clh-docker CI here, and we believe the instability is likely to be related to the seccomp option in CLH.

To understand and fix the recent instability of the CLH CI, I propose to disable the seccomp option of CLH in Kata for now. In this way, we can separate seccomp related failures from other moving pieces (e.g. packaging clh as real static binary, and new changes from tests/runtime, etc). On the other hand, we can start a separate issue/PR to debug on the seccomp issue in Kata, which we can collect a list of missing syscalls that are required to run Kata workload with CLH (issue #2901 ).

Expected result

Constantly stable CI on CLH.

Actual result

Periodic CI failures that can be resolved by restarting the same CI job. Examples from the clh docker CI are:

Job 191 vs 190/189

Job 184 vs 183

[likebreath]

/cc @jcvenegas @amshinde @egernst @sboeuf @sameo