[Android] Update all Robolectric tests to Robolectric 3.0

ui/android/junit/src/org/chromium/ui/picker/DateDialogNormalizerTest.java

Index: ui/android/junit/src/org/chromium/ui/picker/DateDialogNormalizerTest.java
diff --git a/ui/android/junit/src/org/chromium/ui/picker/DateDialogNormalizerTest.java b/ui/android/junit/src/org/chromium/ui/picker/DateDialogNormalizerTest.java
index 7f6248063543dbdc325e53fa18edf52494572b7e..ba830dbdd131197ffccb17f0f495ff25801955c7 100644
--- a/ui/android/junit/src/org/chromium/ui/picker/DateDialogNormalizerTest.java
+++ b/ui/android/junit/src/org/chromium/ui/picker/DateDialogNormalizerTest.java
@@ -22,7 +22,7 @@ import java.util.TimeZone;
  * Tests for DateDialogNormalizer.
  */
 @RunWith(LocalRobolectricTestRunner.class)
-@Config(manifest = Config.NONE)
+@Config(manifest = Config.NONE, sdk = 18)

[Ted C, 2016/08/03 19:18:26]

Might have been explained but why do we need to specify sdk?  What does it
actually represent?

Is it the minimum sdk that we expect this to run against?  In which case,
wouldn't we want it to be 16 as the first jellybean release?

If it is just the sdk this is built against, don't we always want the latest?

[mikecase (-- gone --), 2016/08/05 03:17:07]

Robolectric has special versions of the android sdk with classes that are able
to run in your workstations jvm.
You can specify which of these sdks is loaded by Robolectric when running a
test. Previously, only Robolectric's android
sdk 18 was available in Chromium (the highest sdk level supported by Robolectric
2.4). Now I'm adding support for sdk 21
(the highest sdk level supported by Robolectric 3.0) and making it the default
(see LocalRobolectricTestRunner.java 
DEFAULT_ANDROID_SDK).

There are a couple tests that don't seem to work with sdk=21.
In this specific instance, Im hitting this error. 
https://github.com/robolectric/robolectric/issues/2024

Setting sdk=18 (which was what was being used previously) fixes the issue and
seems to be the recommended fix for this issue.

[Ted C, 2016/08/05 20:17:15]

So if you don't specify sdk, do you get the most recent version of the
roboelectric sdk by default (i.e. 21)?

For example,
https://codereview.chromium.org/2195143002/diff/160001/base/test/android/juni...
that test seems to specify 21 despite that being the most up to date one.

Ideally, all our tests would just use the latest version of roboelectric and
"just work".  I'd prefer to just have to specify the sdk if the new one breaks
an existing tests (and I'd prefer they have a crbug associated with each one
that maybe just points to the roboelectric bug you found...ideally, these tests
would update to the newer sdk once the bug in the underlying framework was
addressed).

Buuut..if it doesn't pick up a default sdk, then I guess this is what we'll have
to do.

 public class DateDialogNormalizerTest {
 
     private static final long MILLIS_PER_MINUTE = 60 * 1000;