The idea is to implement a locking mechanism that utilizes the backupstore,
to prevent the following dangerous cases of concurrent operations.
1. prevent backup deletion during backup restoration
2. prevent backup deletion while a backup is in progress
3. prevent backup creation during backup deletion
4. prevent backup restoration during backup deletion
The locking solution shouldn't unnecessary block operations, so the
following cases should be allowed.
1. allow backup creation during restoration
2. allow backup restoration during creation
The locking solution should have a maximum wait time for lock acquisition,
which will fail the backup operation so that the user does not have to wait
forever.
The locking solution should be self expiring, so that when a process dies
unexpectedly, future processes are able to acquire the lock.
The locking solution should guarantee that only a single type of lock is
active at a time.
The locking solution should allow a lock to be passed down into async
running go routines.
Longhorn #612
Signed-off-by: Joshua Moody <joshua.moody@rancher.com>
