fix(localpv-hostpath): pv deletion caused panic when node not found

[kmova]

Ref #1662

After the PV is created and node affinity is set
based on kubernetes.io/hostname label, either:

• hostname label changed on the node or
• the node is deleted from the cluster.

This PR fixes the panic, by logging the details
of the node hostname that no longer exists
in the cluster.

The code doesn't force delete the PV, considering that
the node might intermittently be out of the cluster.

If the user decides that node is not going to come back,
then the user can go ahead with force delete of pv using
kubectl delete pv.

An alternate case is that node hostname has really changed.
In this case, user will have to perform a manual migration
of the localpv-hostpath PV to the new node using the
following steps:

• Scale down the deployment or sts using the PVC.
• Save the PVC and PV yamls files.
• Delete the PVC and PV
• Modify the saved PV yaml will the node hostname and apply
  Note: when re-applying the yamls, the uuid of pv and pvc objects
  will change, so the metadata around self-uuid,etc needs to be
  cleared.
• Modify the saved PVC yaml for stale references and re-apply.
• Update the PV yaml with the uuid of the newly created PVC
• Scale up the deployment.

Signed-off-by: kmova [email protected]
(cherry picked from commit 728a003)

[vishnuitta]

changes are good