Upgrade kustomize-in-kubectl to v4.0.5

[monopole]

What type of PR is this?

/kind bug
/kind cleanup
/sig cli
/priority important-soon

What this PR does / why we need it:

Fixes kubernetes-sigs/kustomize#1500
Fixes kubernetes/kubectl#818

Special notes for your reviewer:

This PR has these commits:

1. Deletion of staging/src/k8s.io/cli-runtime/pkg/kustomize/k8sdeps.
2. Manual edits to these five files under staging/src/k8s.io/:
   • cli-runtime/pkg/resource/builder.go
   • cli-runtime/pkg/resource/kustomizevisitor.go
   • cli-runtime/pkg/resource/kustomizevisitor_test.go
   • cli-runtime/pkg/resource/visitor.go
   • kubectl/pkg/cmd/kustomize/kustomize.go
3. Runs of update-vendor, lint-dependencies, pin-dependency, update-internal-modules (till linter succeeded).

Only the second commit has manual code edits. The change in kustomizevisitor_test.go is due to a bug fix (kubernetes-sigs/kustomize#1899).

Deletion of the old code results in many dependency upgrades, and associated vendor updates.

Does this PR introduce a user-facing change?:

Updates the commands 
 * kubectl kustomize {arg}
 * kubectl apply -k {arg}
to use same code as kustomize CLI v4.0.5
 - [v4.0.5]: https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv4.0.5

[BenTheElder]

1. these files should not be checked in and are left behind by buggy unit tests: unit tests leaving behind xtables.lock #98947

• pkg/util/iptables/xtables-103516112.lock
• pkg/util/iptables/xtables-103657263.lock
• pkg/util/iptables/xtables-104036897.lock

2. This is a pretty huge diff 😬
3. Some of the dependencies appear to be under licenses that are not approved by the CNCF

Does this totally resolve the k8sdeps thing?

[ehashman]

/remove-sig instrumentation
/remove-sig node
/assign @dims

[monopole]

@dims, thanks. Just pushed a fresh rebase.

[liggitt]

/lgtm

[monopole]

/test pull-kubernetes-integration

[liggitt]

/skip

[fedebongio]

/triage accepted