Prepare profiler test for try-catch being optimizable.

Prepare profiler test for try-catch being optimizable.

This is an adaptation of test-profile-generator/BailoutReason to when
try-catch statements are optimizable. They will no longer cause any
bailout reason to be reported.

R=yangguo@chromium.org
TEST=cctest/test-profile-generator/BailoutReason

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

[Michael Starzinger, 2015-07-01 13:38:59]

Please advise if there are any folks from the DevTools side that we should
notify about this.

[Yang, 2015-07-02 08:25:09]

On 2015/07/01 13:38:59, Michael Starzinger wrote:
> Please advise if there are any folks from the DevTools side that we should
> notify about this.

Not sure whether Yury is is interested in this.

[Yang, 2015-07-02 08:25:31]

yangguo@chromium.org changed reviewers:
+ yurys@chromium.org

[yurys, 2015-07-02 08:51:20]

LGTM. Thanks for keeping us posted and good to hear that try-catch are going to
be optimizable.

[Michael Starzinger, 2015-07-02 09:21:09]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2015-07-02 09:21:23]

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

[commit-bot: I haz the power, 2015-07-02 09:22:53]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-07-02 09:23:02]

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