Ensure correct screen size is set before widget bounds are calculated.

[kalyankondapally]

Chrome needs the screen size quite early for calculating widget bounds. Chrome does this calculation even before GPU Process is forked. Thus, Forcing IPC communication between GPU process and Browser process at a early stage doesn't help here.

Possible solutions:
1)Have a env variable like Ozone does.
2)Read from weston.ini file or from same place wayland gets this information?
3)Create a temporary wayland client connection on browser process side, get screen output and close it ? As this is an issue only at start up.

[tiagovignatti]

Both 1. and 2. are not robust enough for output hotplug cases, i.e. automatically getting new displays configuration dynamically. And I think that 3. does the intended best here. I'll be exploring this idea further soon.

[kalyankondapally]

fixed: 40fa0f2