GitLab

This change tries to use more of the Chrome stack for our integration
tests. This might catch errors in the bridge that previously let compile
failures slip.
This *might* increase robustness because the calls of the native bridge
are now correct and don't have to be replaced anymore. This caused some
weird cases where the bridge would say: display nothing and the test
quickly called *DO* display something.

The overhead shouldn't increase much, since we don't actually load the
test data from the render but instead fill the cache of the native part
of the component.
This allows the native side to behave naturally and even fill tapped
suggestions as it normally would.

A small clean-up that supported this change: the EmbeddedTestServer
allows loading html pages which provides an IP as origin instead of
a data url.

Bug: 913888, 894428, 922131, 920901
Change-Id: Ib2c09ed386354965ccdaf2f44ca1aafd218fd018
Reviewed-on: https://chromium-review.googlesource.com/c/1448233
Commit-Queue: Friedrich [CET] <fhorschig@chromium.org>
Reviewed-by: Fabio Tirelo <ftirelo@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Reviewed-by: Ioana Pandele <ioanap@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629964}