internal/cri: log ctr's exit event on info level

[ningmingxiao]

No description provided.

[k8s-ci-robot]

Hi @ningmingxiao. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ningmingxiao]

sometimes I want to know when container is exited,but default log level is info will not print exited events
some issue:#10025

[ktock]

Why not --log-level debug?

[ningmingxiao]

Why not --log-level debug?
--log-level debug will generate many logs and it is easy to cause logroate, many of them are not important.

[fuweid]

LGTM

It's acceptable to me.