Removes explicit shutdown of TabRestoreService in ~Browser

This code is no longer needed. Early versions of TRS took ownership of the
NavigationController, hence destruction issues. That hasn't been the case for a long time.

One of the problem with early destruction is connected with chrome.sessions api, while we create window - create incognito window - close the first window, TabRestoreService is destroyed, and there is no any possibility to have events on
sessions.onChanged() for the new windows for profiles.

This pr is based on discussion in
https://codereview.chromium.org/1642583002/

R=Delvin@chromium.org,sky@chromium.org
BUG=

Committed: https://crrev.com/e5ab691aceb914c2e305ab6887f2598961ca768c
Cr-Commit-Position: refs/heads/master@{#373754}

[reat, 2016-02-03 10:57:34]

Patch which removes obsolete code.

[sky, 2016-02-03 17:22:18]

Please change the title to something like: "Removes explicit shutdown of
TabRestoreService in ~Browser"

You can also say something like:
"This code is no longer needed. Early versions of TRS took ownership of the
NavigationController,
hence destruction issues. That hasn't been the case for a long time."

And then add your comments about the issues early destruction causes.

[reat, 2016-02-04 06:04:22]

Description was changed from

==========
Fix bug with invalid chrome.sessions.onChanged listener.

When we have call chains like:
1. Create browser, register chrome.sessions.onChanged listener.
2. Create incognito window.
3. Close previous normal browser window.
4. Create new normal browser window.
5. Close incognito window.
6. Register chrome.sessions.onChanged listener.

TabRestoreService destroyed, but it should not, because:
@sky: "Early versions of TRS took ownership of the NavigationController,
hence destruction issues. That hasn't been the case for a long time.
So, I think the code in browser can be removed, <...>"

This pr is based on discussion in
https://codereview.chromium.org/1642583002/

R=Delvin@chromium.org,sky@chromium.org
BUG=
==========

to

==========
This code is no longer needed. Early versions of TRS took ownership of the
NavigationController, hence destruction issues. That hasn't been the case for a
long time.

One of the problem with early destruction is connected with chrome.sessions api,
while we create window - create incognito window - close the first window,
TabRestoreService is destroyed, and there is no any possibility to have events
on
sessions.onChanged() for the new windows for profiles.

This pr is based on discussion in
https://codereview.chromium.org/1642583002/

R=Delvin@chromium.org,sky@chromium.org
BUG=
==========

[reat, 2016-02-04 06:04:51]

I update issue.

[sky, 2016-02-04 17:31:19]

Thanks, LGTM

[reat, 2016-02-05 04:43:53]

The CQ bit was checked by reat@yandex-team.ru

[commit-bot: I haz the power, 2016-02-05 04:44:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1667683002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1667683002/1

[commit-bot: I haz the power, 2016-02-05 04:46:17]

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

[commit-bot: I haz the power, 2016-02-05 04:46:17]

Try jobs failed on following builders:
  ios_dbg_simulator_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)

[reat, 2016-02-05 05:00:27]

The CQ bit was checked by reat@yandex-team.ru

[reat, 2016-02-05 05:00:28]

The patchset sent to the CQ was uploaded after l-g-t-m from sky@chromium.org
Link to the patchset: https://codereview.chromium.org/1667683002/#ps20001
(title: "Fix patch")

[commit-bot: I haz the power, 2016-02-05 05:02:55]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1667683002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1667683002/20001

[commit-bot: I haz the power, 2016-02-05 05:48:38]

Description was changed from

==========
This code is no longer needed. Early versions of TRS took ownership of the
NavigationController, hence destruction issues. That hasn't been the case for a
long time.

One of the problem with early destruction is connected with chrome.sessions api,
while we create window - create incognito window - close the first window,
TabRestoreService is destroyed, and there is no any possibility to have events
on
sessions.onChanged() for the new windows for profiles.

This pr is based on discussion in
https://codereview.chromium.org/1642583002/

R=Delvin@chromium.org,sky@chromium.org
BUG=
==========

to

==========
This code is no longer needed. Early versions of TRS took ownership of the
NavigationController, hence destruction issues. That hasn't been the case for a
long time.

One of the problem with early destruction is connected with chrome.sessions api,
while we create window - create incognito window - close the first window,
TabRestoreService is destroyed, and there is no any possibility to have events
on
sessions.onChanged() for the new windows for profiles.

This pr is based on discussion in
https://codereview.chromium.org/1642583002/

R=Delvin@chromium.org,sky@chromium.org
BUG=
==========

[commit-bot: I haz the power, 2016-02-05 05:48:38]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-02-05 05:49:21]

Description was changed from

==========
This code is no longer needed. Early versions of TRS took ownership of the
NavigationController, hence destruction issues. That hasn't been the case for a
long time.

One of the problem with early destruction is connected with chrome.sessions api,
while we create window - create incognito window - close the first window,
TabRestoreService is destroyed, and there is no any possibility to have events
on
sessions.onChanged() for the new windows for profiles.

This pr is based on discussion in
https://codereview.chromium.org/1642583002/

R=Delvin@chromium.org,sky@chromium.org
BUG=
==========

to

==========
This code is no longer needed. Early versions of TRS took ownership of the
NavigationController, hence destruction issues. That hasn't been the case for a
long time.

One of the problem with early destruction is connected with chrome.sessions api,
while we create window - create incognito window - close the first window,
TabRestoreService is destroyed, and there is no any possibility to have events
on
sessions.onChanged() for the new windows for profiles.

This pr is based on discussion in
https://codereview.chromium.org/1642583002/

R=Delvin@chromium.org,sky@chromium.org
BUG=

Committed: https://crrev.com/e5ab691aceb914c2e305ab6887f2598961ca768c
Cr-Commit-Position: refs/heads/master@{#373754}
==========

[commit-bot: I haz the power, 2016-02-05 05:49:22]

Patchset 2 (id:??) landed as
https://crrev.com/e5ab691aceb914c2e305ab6887f2598961ca768c
Cr-Commit-Position: refs/heads/master@{#373754}