Use 'sieve' to check for distributed/concurrency related issues in kapp-controller

**Describe the problem/challenge you have**
It's very hard to prove the absence of bugs, and classically this class of bugs is very hard to find/detect/reproduce

**Describe the solution you'd like**
luckily for us, some folks at vmware and UIUC are working on this "sieve" tool: https://github.com/sieve-project/sieve

**Anything else you would like to add:**
Note that sieve is marketed as still in very early stages; imo this would be interesting to explore but if it's rocky we would have the options of reaching out directly for assistance and/or putting this thought onto the back-burner for a few months and coming back to see if the tool is more mature.

Note also that the sieve tool is described in the kube-con talk "Automated, Distributed Systems Testing for Kubernetes Controllers - Lalith Suresh, VMware & Xudong Sun, University of Illinois at Urbana-Champaign"

---
Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.