Support additional apply mechanism -- server side apply

**Describe the problem/challenge you have**
I'd like make use of server side apply feature, bypassing rebaseRule entirely.

**Describe the solution you'd like**

An optional support for server-side apply, enabled by the `--server-side` flag.

**Anything else you would like to add:**

When server-side apply is in use rebaseRules are entirely bypassed. Diff is generated using dry run and diffing result with kubernetes objects currently in cluster to get a most accurate preview of changes.

Should server side apply generate a conflict, it can be resolved in kapp favour with `--force` flag.

`kapp.k14s.io/original` annotation remains populated to support subsequent kapp invocations without `--server-side` flag. Default rebaseRules probably need to be updated to keep cluster-managed `metadata.managedFields` path.

Related issues: https://github.com/vmware-tanzu/carvel-kapp/issues/43

Server side apply doc: https://kubernetes.io/docs/reference/using-api/server-side-apply/

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