Provide a way for kapp-controller to not take ownership of existing resources

[**Describe the problem/challenge you have**
When deploying a package, if there's a resource defined in the package contents that already exist in the cluster, kapp will take ownership of this resource. From that moment, if the package is removed, then the existing resource will be removed as well.

**Describe the solution you'd like**
I would want to have an annotation on the package that defines whether existing resources should be absorbed as owned or not, so that if the annotation is present and the resource exists, kapp-controller reconciliation will fail indicating that the resource already exists and that can not be claimed as owned by the package. This will prevent taking incorrectly ownership of existing namespaces, and similar problems.

**Anything else you would like to add:**
This is a conversation that unveiled this problem: https://kubernetes.slack.com/archives/C02GY94A8KT/p1645018465370589

---
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.