text: Title: before-first-apply manager prevents resource updates
  Body: <!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
  
  If the matter is security related, please disclose it privately via https://kubernetes.io/security/
  -->
  
  
  **What happened**:
  
  This problem is occurred when trying to do server-side apply without force option.
  I cannot apply new patch to the resource which was created by client-side apply.
  It is because `before-first-apply` manager prevents resource updates by other manager's server-side apply.
  
  What is `before-first-apply` field manager?
  Of course it can be patched if the force-conflicts option is added to the request, however is this the intended behavior of kube-apiserver?
  
  
  **What you expected to happen**:
  
  It is enable to do server-side apply without force option to the resource which was created by client-side apply.
  
  **How to reproduce it (as minimally and precisely as possible)**:
  
  1. Prepare pod manifest. 
  ```console
  $ cat pause.yaml
  apiVersion: v1
  kind: Pod
  metadata:
    name: pause
    namespace: sandbox
  spec:
    containers:
    - image: k8s.gcr.io/pause:latest
      name: pause
  ```
  2. Apply it by client-side-apply
  ```console
  $ kubectl apply -f pause.yaml
  pod/pause created
  ```
  3. Apply the same manifest by server-side apply
  ```console
  $ kubectl apply -f pause.yaml --server-side
  pod/pause serverside-applied
  ```
  4. Prepare the tweaked pod manifest.
  ```console
  $ sed s/pause:latest/pause:3.1/g pause.yaml > pause-3-1.yaml
  ```
  5. Apply the tweaked manifest by server-side apply without `--force-conflicts` option.
  ```console
  $ kubectl apply -f pause-3-1.yaml --server-side
  error: Apply failed with 1 conflict: conflict with "before-first-apply" using v1: .spec.containers[name="pause"].image
  
  Please review the fields above--they currently have other managers. Here
  are the ways you can resolve this warning:
  * If you intend to manage all of these fields, please re-run the apply
    command with the `--force-conflicts` flag.
  * If you do not intend to manage all of the fields, please edit your
    manifest to remove references to the fields that should keep their
    current managers.
  * You may co-own fields by updating your manifest to match the existing
    value; in this case, you'll become the manager if the other manager(s)
    stop managing the field (remove it from their configuration).
  
  See http://k8s.io/docs/reference/using-api/api-concepts/#conflicts
  ```
  
  **Anything else we need to know?**:
  
  **Environment**:
  - Kubernetes version (use `kubectl version`): 
  ```console
  $ kubectl version
  Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-12T21:03:42Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
  Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"archive", BuildDate:"2020-03-13T04:17:19Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
  ```
  - Cloud provider or hardware configuration: on-premiss
  - OS (e.g: `cat /etc/os-release`):
  ```console
  $ cat /etc/os-release
  NAME="Ubuntu"
  VERSION="18.04.4 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/"
  SUPPORT_URL="https://help.ubuntu.com/"
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic
  ```
  - Kernel (e.g. `uname -a`):
  ```console
  $ uname -a
  Linux stage0-boot-0 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  ```
  - Install tools: [in-house tool](https://landscape.cncf.io/format=card-mode&grouping=category&organization=cybozu&selected=cybozu-kubernetes-engine)
  - Network plugin and version (if this is a network-related bug):
  - Others:
  