Remove extra reboot from optimized restore

Optimized restore was triggering an SM reboot upon
completion.  This reboot has been removed and unlocking
is now possible directly after restore is complete.

Use "-e 'restore_mode=optimized'" to use the optimized playbook.

Current Usage:
1 - restore_platform.yml -e "backup_filename=${BACKUP_FILENAME} \
registry_backup_filename=${REGISTRY_BACKUP_FILENAME} \
restore_mode=optimized"
2 - source /etc/platform/openrc
3 - system host-unlock controller-0

On-going development issues, currently being addressed:
Kubelet/etcd not working after unlock.
Some LDAP issues also present.

TEST PLAN:
PASS: Install/bootstrap/unlock (SX/DX/STD) must not be impacted
PASS: Original restore (SX/DX/STD) must not be impacted
PASS: Optimized restore can be unlocked upon completion (SX)
  No reboots if system is left idle and locked.
  *System does not currently work after unlocking.

Story: 2010117
Task: 46505
Depends-On: https://review.opendev.org/c/starlingx/stx-puppet/+/861233
Change-Id: Ibb2fed8ceba77024479824c345431755d2a077fa

playbookconfig/src/playbooks/roles/bootstrap/bringup-essential-services/tasks/main.yml

@@ -37,8 +37,9 @@
     when: last_config_file_exists and reconfigure_endpoints and
           (mgmt_floating_virtual != prev_mgmt_floating_virtual)
 
-  - name: Mount current kubernetes version
-    import_tasks: k8s_bind_mount.yml
+  - name: Mount current Kubernetes version
+    import_role:
+      name: common/k8s-bind-mount
 
   - name: Refresh local DNS (i.e. /etc/hosts)
     import_tasks: refresh_local_dns.yml