[Reland] Use dropdown list for admin areas in pr form.

Reland explanation: crrev.com/2680143002 caused chrome_public_test_apk
failing on chromium.android/Marshmallow. The problem is fixed in this
CL.

To make the payment request tests independent of the network status,
the tests set the time-out = 0,
which means that the sub-keys must never be fetched,
and the address forms will always show a textfield, 
and not a dropdown for the admin areas. 

In the previous CL, the time-out would start after the request.
=> For some entities (with network connection),
subkeys were already fetched, before the timeout had started.
=> A dropdown would show.

To solve this, the order was changed.
Now the time-out starts before the request.   


BUG=709491
Review-Url: https://codereview.chromium.org/2812893002
Cr-Commit-Position: refs/heads/master@{#463945}
Committed: https://chromium.googlesource.com/chromium/src/+/886089f3cad28e46fa21e3d73c60fd5e87d7621f

[Parastoo, 2017-04-11 10:05:42]

The CQ bit was checked by parastoog@google.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-11 10:05:58]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Parastoo, 2017-04-11 10:06:21]

The CQ bit was checked by parastoog@google.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-11 10:06:32]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Parastoo, 2017-04-11 10:08:11]

Description was changed from

==========
Use drop-down list for admin areas (state, province, ..)

-- In the payment request form (instead of the previous text-field).

- For this purpose, the rules of the specified country are loaded from
 the i18n aggregate server, and the country's sub-keys are retrieved from the
right rule.

- If the server doesn't respond, or there is a time-out, or if no
  admin areas are recorded for that country, show text-field.

   -- Add all the fields to the form, only when admin areas are loaded.
      This way we can have the fields in order. Otherwise, admin areas
      would show up at the end (since they are fetched asynchronously.)

- In the Payment Request tests, the admin area field would always be a
  text field (and not a drop down). This way, the tests would be
  independent of the network connection state.

- Tests were added to the AddressValidatorTest according to the
  changes.

BUG=675634

Review-Url: https://codereview.chromium.org/2680143002
Cr-Commit-Position: refs/heads/master@{#462611}
Committed:
https://chromium.googlesource.com/chromium/src/+/69b196d676ecbbb986009aaf9f56...

patch from issue 2680143002 at patchset 1000001
(http://crrev.com/2680143002#ps1000001)
==========

to

==========
BUG=709491
==========

[commit-bot: I haz the power, 2017-04-11 10:18:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-04-11 10:18:12]

Dry run: Try jobs failed on following builders:
  chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[Parastoo, 2017-04-11 15:04:29]

Description was changed from

==========
BUG=709491
==========

to

==========
CL 2680143002 caused chrome_public_test_apk failing on
chromium.android/Marshmallow. The problem is fixed in this CL. 


BUG=709491
==========

[Parastoo, 2017-04-11 15:46:13]

The CQ bit was checked by parastoog@google.com to run a CQ dry run

[commit-bot: I haz the power, 2017-04-11 15:46:49]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Parastoo, 2017-04-11 16:30:56]

Description was changed from

==========
CL 2680143002 caused chrome_public_test_apk failing on
chromium.android/Marshmallow. The problem is fixed in this CL. 


BUG=709491
==========

to

==========
CL 2680143002 caused chrome_public_test_apk failing on
chromium.android/Marshmallow. The problem is fixed in this CL. 

To make the payment request tests independent of the network status,
the tests set the time-out = 0,
which means that the sub-keys must never be fetched,
and the address forms will always show a textfield, 
and not a dropdown for the admin areas. 

In the previous CL, the time-out would start after the request.
=> For some entities (with network connection),
sub-keys were already fetched, before the timeout had started.
=> A dropdown would show.

To solve this, the order was changed.
Now the time-out starts before the request.   


BUG=709491
==========

[Parastoo, 2017-04-11 16:32:15]

parastoog@google.com changed reviewers:
+ mathp@chromium.org, sebsg@chromium.org

[Parastoo, 2017-04-11 16:32:28]

Patchset #2 (id:20001) has been deleted

[commit-bot: I haz the power, 2017-04-11 16:33:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-04-11 16:33:40]

Dry run: This issue passed the CQ dry run.

[Parastoo, 2017-04-11 16:38:29]

Description was changed from

==========
CL 2680143002 caused chrome_public_test_apk failing on
chromium.android/Marshmallow. The problem is fixed in this CL. 

To make the payment request tests independent of the network status,
the tests set the time-out = 0,
which means that the sub-keys must never be fetched,
and the address forms will always show a textfield, 
and not a dropdown for the admin areas. 

In the previous CL, the time-out would start after the request.
=> For some entities (with network connection),
sub-keys were already fetched, before the timeout had started.
=> A dropdown would show.

To solve this, the order was changed.
Now the time-out starts before the request.   


BUG=709491
==========

to

==========
CL 2680143002 caused chrome_public_test_apk failing on
chromium.android/Marshmallow. The problem is fixed in this CL. 

To make the payment request tests independent of the network status,
the tests set the time-out = 0,
which means that the sub-keys must never be fetched,
and the address forms will always show a textfield, 
and not a dropdown for the admin areas. 

In the previous CL, the time-out would start after the request.
=> For some entities (with network connection),
subkeys were already fetched, before the timeout had started.
=> A dropdown would show.

To solve this, the order was changed.
Now the time-out starts before the request.   


BUG=709491
==========

[sebsg, 2017-04-11 17:04:06]

Makes sense, thanks for the fix.

I would change the name to something like "Reland of *insert original CL name
here" or something. Maybe Math knows the expected format.

LGTM

[Mathieu, 2017-04-11 18:34:34]

Description was changed from

==========
CL 2680143002 caused chrome_public_test_apk failing on
chromium.android/Marshmallow. The problem is fixed in this CL. 

To make the payment request tests independent of the network status,
the tests set the time-out = 0,
which means that the sub-keys must never be fetched,
and the address forms will always show a textfield, 
and not a dropdown for the admin areas. 

In the previous CL, the time-out would start after the request.
=> For some entities (with network connection),
subkeys were already fetched, before the timeout had started.
=> A dropdown would show.

To solve this, the order was changed.
Now the time-out starts before the request.   


BUG=709491
==========

to

==========
Reland explanation: crrev.com/2680143002 caused chrome_public_test_apk
failing on chromium.android/Marshmallow. The problem is fixed in this
CL.

To make the payment request tests independent of the network status,
the tests set the time-out = 0,
which means that the sub-keys must never be fetched,
and the address forms will always show a textfield, 
and not a dropdown for the admin areas. 

In the previous CL, the time-out would start after the request.
=> For some entities (with network connection),
subkeys were already fetched, before the timeout had started.
=> A dropdown would show.

To solve this, the order was changed.
Now the time-out starts before the request.   


BUG=709491
==========

[Mathieu, 2017-04-11 18:35:02]

lgtm

[Parastoo, 2017-04-11 19:25:12]

parastoog@google.com changed reviewers:
+ dfalcantara@chromium.org, rouslan@chromium.org

[gone, 2017-04-11 20:03:00]

lgtm

[please use gerrit instead, 2017-04-11 21:14:37]

lgtm

[Parastoo, 2017-04-12 06:59:07]

The CQ bit was checked by parastoog@google.com

[commit-bot: I haz the power, 2017-04-12 06:59:39]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-12 07:44:17]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1491980347921440,
"parent_rev": "39f8e8cde10ced24bf0dbcae7187995221f009fe", "commit_rev":
"886089f3cad28e46fa21e3d73c60fd5e87d7621f"}

[commit-bot: I haz the power, 2017-04-12 07:45:30]

Description was changed from

==========
Reland explanation: crrev.com/2680143002 caused chrome_public_test_apk
failing on chromium.android/Marshmallow. The problem is fixed in this
CL.

To make the payment request tests independent of the network status,
the tests set the time-out = 0,
which means that the sub-keys must never be fetched,
and the address forms will always show a textfield, 
and not a dropdown for the admin areas. 

In the previous CL, the time-out would start after the request.
=> For some entities (with network connection),
subkeys were already fetched, before the timeout had started.
=> A dropdown would show.

To solve this, the order was changed.
Now the time-out starts before the request.   


BUG=709491
==========

to

==========
Reland explanation: crrev.com/2680143002 caused chrome_public_test_apk
failing on chromium.android/Marshmallow. The problem is fixed in this
CL.

To make the payment request tests independent of the network status,
the tests set the time-out = 0,
which means that the sub-keys must never be fetched,
and the address forms will always show a textfield, 
and not a dropdown for the admin areas. 

In the previous CL, the time-out would start after the request.
=> For some entities (with network connection),
subkeys were already fetched, before the timeout had started.
=> A dropdown would show.

To solve this, the order was changed.
Now the time-out starts before the request.   


BUG=709491

Review-Url: https://codereview.chromium.org/2812893002
Cr-Commit-Position: refs/heads/master@{#463945}
Committed:
https://chromium.googlesource.com/chromium/src/+/886089f3cad28e46fa21e3d73c60...
==========

[commit-bot: I haz the power, 2017-04-12 07:45:31]

Committed patchset #2 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/886089f3cad28e46fa21e3d73c60...

[Donn Denman, 2017-04-12 17:20:55]

A revert of this CL (patchset #2 id:40001) has been created in
https://codereview.chromium.org/2817733002/ by donnd@chromium.org.

The reason for reverting is: Still some lingering test failures.  See
crbug.com/710911.