Revert of Update AuraInit to handle failed initialization

Revert of Update AuraInit to handle failed initialization (patchset #2 id:40001 of https://codereview.chromium.org/2967943002/ )

Reason for revert:
Causing chrome --mash to fail to start

[118236:118236:0706/142624.101546:3509128143561:ERROR:chrome_main_delegate.cc(1187)] Main process exiting because service ash quit unexpectedly.


Original issue's description:
> It is possible for AuraInit to fail initialization. If the remote ServiceManager closes while a Service is starting up, then the synchronous calls to Directory will fail before error states are received.
> 
> This change follows up a previous change to AuraInit and QuickLauncher which was addressing these crashes in unittests. It refactors AuraInit to have an explicit initialization method. All callsites are updated to check the success of init, and to close cleanly upon failures.
> 
> TBR=sky@chromium.org
> TEST=mash_browser_tests
> BUG=678687
> 
> Review-Url: https://codereview.chromium.org/2967943002
> Cr-Commit-Position: refs/heads/master@{#484583}
> Committed: https://chromium.googlesource.com/chromium/src/+/14402447b7df16d16126dc49a3a44cf66c318c88

TBR=sadrul@chromium.org,sky@chromium.org,jonross@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=678687
Review-Url: https://codereview.chromium.org/2973103002
Cr-Commit-Position: refs/heads/master@{#484711}
Committed: https://chromium.googlesource.com/chromium/src/+/e3f9dbb7b50ab80caf29071bef886c2ec8cee28c

[Fady Samuel, 2017-07-06 19:32:40]

The CQ bit was checked by fsamuel@chromium.org

[Fady Samuel, 2017-07-06 19:32:40]

Created Revert of Update AuraInit to handle failed initialization

[commit-bot: I haz the power, 2017-07-06 19:33:02]

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-07-06 19:33:32]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1499369560591050, "parent_rev":
"b5ac971cfbf3afa2230534369912bffccefb0fc1", "commit_rev":
"e3f9dbb7b50ab80caf29071bef886c2ec8cee28c"}

[commit-bot: I haz the power, 2017-07-06 19:33:54]

Description was changed from

==========
Revert of Update AuraInit to handle failed initialization (patchset #2 id:40001
of https://codereview.chromium.org/2967943002/ )

Reason for revert:
Causing chrome --mash to fail to start

[118236:118236:0706/142624.101546:3509128143561:ERROR:chrome_main_delegate.cc(1187)]
Main process exiting because service ash quit unexpectedly.


Original issue's description:
> It is possible for AuraInit to fail initialization. If the remote
ServiceManager closes while a Service is starting up, then the synchronous calls
to Directory will fail before error states are received.
> 
> This change follows up a previous change to AuraInit and QuickLauncher which
was addressing these crashes in unittests. It refactors AuraInit to have an
explicit initialization method. All callsites are updated to check the success
of init, and to close cleanly upon failures.
> 
> TBR=sky@chromium.org
> TEST=mash_browser_tests
> BUG=678687
> 
> Review-Url: https://codereview.chromium.org/2967943002
> Cr-Commit-Position: refs/heads/master@{#484583}
> Committed:
https://chromium.googlesource.com/chromium/src/+/14402447b7df16d16126dc49a3a4...

TBR=sadrul@chromium.org,sky@chromium.org,jonross@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=678687
==========

to

==========
Revert of Update AuraInit to handle failed initialization (patchset #2 id:40001
of https://codereview.chromium.org/2967943002/ )

Reason for revert:
Causing chrome --mash to fail to start

[118236:118236:0706/142624.101546:3509128143561:ERROR:chrome_main_delegate.cc(1187)]
Main process exiting because service ash quit unexpectedly.


Original issue's description:
> It is possible for AuraInit to fail initialization. If the remote
ServiceManager closes while a Service is starting up, then the synchronous calls
to Directory will fail before error states are received.
> 
> This change follows up a previous change to AuraInit and QuickLauncher which
was addressing these crashes in unittests. It refactors AuraInit to have an
explicit initialization method. All callsites are updated to check the success
of init, and to close cleanly upon failures.
> 
> TBR=sky@chromium.org
> TEST=mash_browser_tests
> BUG=678687
> 
> Review-Url: https://codereview.chromium.org/2967943002
> Cr-Commit-Position: refs/heads/master@{#484583}
> Committed:
https://chromium.googlesource.com/chromium/src/+/14402447b7df16d16126dc49a3a4...

TBR=sadrul@chromium.org,sky@chromium.org,jonross@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=678687

Review-Url: https://codereview.chromium.org/2973103002
Cr-Commit-Position: refs/heads/master@{#484711}
Committed:
https://chromium.googlesource.com/chromium/src/+/e3f9dbb7b50ab80caf29071bef88...
==========

[commit-bot: I haz the power, 2017-07-06 19:33:55]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/e3f9dbb7b50ab80caf29071bef88...