[CPDEV-106079] add containerd health check after restart

[koryaga]

Description

• containerd configuration procedure doesn't wait that containred daemon is healthy after restart. This may cause to issue when containerd daemon is not ready yet and cri request fails.

Fixes # (issue)
Possible way to reproduce:

# systemctl stop containerd; systemctl start containerd && systemctl status --no-pager containerd ; crictl info
...
FATA[0000] validate service connection: validate CRI v1 runtime API for endpoint "unix:///run/containerd/containerd.sock": rpc error: code = Unknown desc = server is not initialized yet

Solution

• To add containerd health check in containerd configuration procedure using active polling with 10 sec timout

How to apply

Test Cases

TestCase 1

Steps:

Results:

Before	After

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• Integration CI passed
• Unit tests. If Yes list of new/changed tests with brief description
• There is no merge conflicts

Unit tests

Indicate new or changed unit tests and what they do, if any.