Optimize the wait time for kubelet upgrade phase in VIM

[Vanathi Selvaraju]

Brief Description
-----------------
As part of kubernetes upgrade using VIM orchestrator, kubelet upgrade phase has a wait time of 60 sec, before checking if the kubelet upgrade is complete. This wait time is not required as we have a timeout and retry mechanism in place.

Severity
--------
Minor

Steps to Reproduce
------------------
Deploy AIO-DX system and use kubernetes_version: 1.21.8 in the localhost.yml during installation
of system controller.

1. Create a strategy to upgrade k8s on the System Controller to v1.22.5
   sw-manager kube-upgrade-strategy create --to-version v1.22.5
2. Apply strategy
   sw-manager kube-upgrade-strategy apply

Expected Behavior
------------------
Successful kubernetes upgrade without a delay of 60 sec in the kubelet phase.

Actual Behavior
----------------
Successful kubernetes upgrade with a delay of 60 sec in the kubelet phase.

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
AIO-DX, Distributed cloud

Branch/Pull Time/Commit
-----------------------
2023-11-23_22-44-25

Test Activity
-------------
Developer testing

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/nfv/+/902710
Committed: https://opendev.org/starlingx/nfv/commit/42442c85d9d351de72d2c20d157866a0c8a1c6ff
Submitter: "Zuul (22348)"
Branch: master

commit 42442c85d9d351de72d2c20d157866a0c8a1c6ff
Author: Vanathi.Selvaraju <email address hidden>
Date: Tue Dec 5 13:31:37 2023 -0500

    Optimize kubelet upgrade phase using VIM orchestrator.

    Optimizing kubelet upgrade by reducing the wait
    time and adding in more logs for debugging.The
    wait time is removed as we have the additional
    kubelet state check in place (Closes-Bug: 2044209)
    and an existing timeout of 900secs.

    Test Plan:
    PASSED: On a DX system, removed the wait time of 60 sec
    and tested 3 consecutive k8s upgrade thrice.
    PASSED: On a DX system, tweaked the code and tested
    on the kubelet upgrade retry timeout(900sec).
    PASSED: On a DX system, tweaked code and tested
    the existing behaviour that retry is not
    occuring in case of failure.

    Closes-Bug: 2045776

    Change-Id: I321d7eae5ef7ebd29c1c6aca97992e3e20acb457
    Signed-off-by: Vanathi.Selvaraju <email address hidden>