Currently chrome skips this process when chrome crashes or restarted during login.
Chrome should always send the start mini container request so that chrome can send
density information.

Background:

Density used for ARC++ is currently resolved in ebuild file,
which has several drawbacks.
1) It requires manual configuration
2) one board may be used for different devices that have differnet
 panels, so one density may not work for other device, even if
 they use the same board configuration.

I'm working on a permanent fix for issue like this b/112574716,
and need to send density when starting mini container because SF reads this property.