Add kernel message on integration test failure

[joshjms]

Summary

In this PR, running separate instances of firecracker-containerd also produces the same flake. Adding kernel message logging on failure might help us debug the cause.

Ref: #1113

Implementation Notes ⚒️

• Briefly outline the overall technical solution. If necessary, identify talking points where the reviewer's attention should be drawn to.

External Dependencies 🍀

Breaking API Changes ⚠️

Simply specify none (N/A) if not applicable.

[joshjms]

Hmm, the kernel messages don't seem to help.

[joshjms]

I think that even if this doesn't help for the current flake issue, it might help us debug for future errors.

cc @leokondrashov

[leokondrashov]

Kernel messages are unlikely to be helpful; it would be more appropriate to collect Firecracker/containerd/vhive logs.

[joshjms]

I agree, although I think that there will be no harm done with including the kernel messages to debug containerd for a more comprehensive logging. This is also used in containerd's CI.