Deoptimize try-catch less radically

[lukastaegert]

This PR contains:

• bugfix
• feature
• refactor
• documentation
• other

Are tests included?

• yes (bugfixes and features will not be merged without tests)
• no

Breaking Changes?

• yes (breaking changes will not be merged unless absolutely necessary)
• no

List any relevant issue numbers:

Description

After reports that the try-catch optimization may be too radical in some instances, this PR will tone it down further. It also includes dedicated regression tests for es5-shim, es6-shim and core-js.

try-statement-deoptimization will now no longer deoptimize functions called from try-catch-blocks, the exception being parameters called if the function is provided directly as an argument.

funtion test(callback) {
  try {
    // callback is included. Tree-shaking inside callback will only occur if it is directly an argument
    callback();
    // call is included but the body of someOtherFunction may be tree-shaken
    someOtherFunction();
  } catch();
}

// is retained as it is
test(() => Object.create(null));

// call is retained but the body of someOtherFunction may be tree-shaken
test(someOtherFunction);

[lukastaegert]

cc @manucorporat