Yeah we don't use this flag anywhere in our tests.

Rohit: Is this here for testing of desktop functionality?

Also we should clear statistics before running any test on our statistics, no?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f1ac06905684c9b963d358d9c778d58df20719f3

commit f1ac06905684c9b963d358d9c778d58df20719f3
Author: rajendrant <rajendrant@chromium.org>
Date: Tue Jan 17 23:48:53 2017

Remove clear-data-reduction-proxy-data-savings flag

clear-data-reduction-proxy-data-savings flag should be removed, since
users may set this mistakenly and later wonder why there are no savings.

BUG= 596625 

Review-Url: https://codereview.chromium.org/2622183002
Cr-Commit-Position: refs/heads/master@{#444192}

[modify] https://crrev.com/f1ac06905684c9b963d358d9c778d58df20719f3/chrome/android/java/src/org/chromium/chrome/browser/snackbar/DataReductionPromoSnackbarController.java
[modify] https://crrev.com/f1ac06905684c9b963d358d9c778d58df20719f3/chrome/browser/about_flags.cc
[modify] https://crrev.com/f1ac06905684c9b963d358d9c778d58df20719f3/components/data_reduction_proxy/core/browser/data_reduction_proxy_compression_stats.cc
[modify] https://crrev.com/f1ac06905684c9b963d358d9c778d58df20719f3/components/data_reduction_proxy/core/browser/data_reduction_proxy_compression_stats_unittest.cc
[modify] https://crrev.com/f1ac06905684c9b963d358d9c778d58df20719f3/components/data_reduction_proxy/core/common/data_reduction_proxy_switches.cc
[modify] https://crrev.com/f1ac06905684c9b963d358d9c778d58df20719f3/components/data_reduction_proxy/core/common/data_reduction_proxy_switches.h