[MANOPD-70719] Verify plugins restart after template applying

[iLeonidze]

Description

• When applying pod template on upgrading, old plugin pods can stuck and kubetools will detect them as already restarted new pods

Fixes MANOPD-70719

Solution

• Added DaemonSet expectation API in cluster.yaml
• Added Deployment expectation API in cluster.yaml
• Added deployment and daemonset expectations to default plugins
• Added time synchronisation validation between nodes after NTP configuring
• Added time synchronisation PAAS check. If time is not synced, test will warn
• Updated docs about time synchronisation between nodes

How to apply

• Nothing to apply

Test Cases

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

TestCase 1

Test Configuration:

• Hardware: Any
• OS: Any
• Inventory: Any

Steps:

1. Start upgrade and make Calico old pods stuck

Results:

Before	After
Installation failed with Calico backend/frontend versions misleading	Installation finished without errors

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

No new unit tests

Reviewers

@koryaga @iLeonidze @Zaborin @alexarefev @Yaroslav-Lahtachev @dmyar21

[iLeonidze]

Please review this PR again after major improvements

[n549]

@iLeonidze what if pods have always the same names (like they do for statefulsets)?

[iLeonidze]

After some discussion, we decided to rework this PR

[alku89]

tested on local qa env. Upgrade procedures finish successfully. issue with the calico plugin not reproduced.