Adapt youki executors when upgrading libcontainer

[0xE282B0]

Youki has changed the way executors are created. The new method is to create a get_executor() function that returns an Executor. The executors in the youki crate can be used as an example: https://github.com/containers/youki/blob/main/crates/youki/src/workload
Instead of the can_handle() function, the executor now returns an ExecutorError::CantHandle(EXECUTOR_NAME) error, which is then handled explicitly like this https://github.com/containers/youki/blob/main/crates/youki/src/workload/executor.rs#L18-L23. This gives more control over the order in which executors are tried.

We need to adapt our executors before upgrading to latest libcontainer version.

[Mossaka]

I can take this one when a new version of libcontainer is released

[utam0k]

cc: @yihuaf 👀

[yihuaf]

@Mossaka Would you mind assign this to me so I can help take care of this? This is also a good exercise for me to understand the ergonomics of the libcontainer apis.

[Mossaka]

Sure!

[0xE282B0]

@yihuaf runwasi now uses libcontainer 0.2. Is there anything else to do here, or can we close this issue?

[Mossaka]

Nope we can close it now