Remove useless use of pref from unit test.

Remove useless use of pref from unit test.

The unit test doesn't need to try and set this pref, since it's only
used by high level UI code to decide what arguments to pass to
BrowsingDataRemover::Remove; the unit test always passes explicit things
to remove that do not include the LSO store.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=111350

[Torne, 2011-11-22 16:57:36]

Hi Bernhard,

Would you mind taking a look at this? This pref set is causing a DCHECK in an
environment where UI-related prefs are not registered; since your change in
http://codereview.chromium.org/8223004 only UI code registers or uses this pref
other than this redundant use in the unit test.

[Bernhard Bauer, 2011-11-22 18:48:50]

Yes, that might be unnecessary. LGTM and thansk for the cleanup!

[commit-bot: I haz the power, 2011-11-23 11:11:12]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/torne@chromium.org/8636014/1

[commit-bot: I haz the power, 2011-11-23 14:01:16]

Change committed as 111350