Setup the sidecar and main container start/shutdown sequence.

### **Describe the bug**
The sidecar currently starts alongside the main container. We would like to make sure the main container does not start before the sidecar has dropped the credential to the bonded volume. In this way, we can clearly identify the problem.

### **Environment**
Please provide the following:
- Hub cluster details
- Member cluster details

### **To Reproduce**
Steps to reproduce the behavior:

### **Expected behavior**
the main container does not start until the hub cluster credential is dropped in.

### **Additional context**

https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/