Deprecate resource usage tracking test in the cluster e2e suite

[yujuhong]

The test was created mainly to track kubelet/docker resource usage. Now that we have node benchmark (http://node-perf-dash.k8s.io/) for this purpose, we can consider retiring the resource usage test. Before we can do that, we need a node e2e soak cluster to catch various resource (cpu, memory) leaks.

/cc @kubernetes/goog-node

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[yujuhong]

Unfortunately this is still needed.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[nikhita]

Removing help-wanted since the directions are not clear enough for a contributor to dive into. Please feel free to re-add the label with more details about how to achieve each step. :)
/remove-help