Increase eval compilation cache hits.

Increase eval compilation cache hits.

This CL introduces two changes to the eval compilation cache. Firstly,
instead of checking for SharedFunctionInfo equivalence to ensure
equivalence of direct eval call sites we now check for Script and
scope start position equivalence.

Furthermore, we increase the cache hits by allowing to share global
eval code for direct and indirect call sites, e.g. in the case
var x = eval; x("12"); eval("12");

Patch from Steven Keuchel <keuchel@chromium.org>;
Original CL: http://codereview.chromium.org/8879010/

BUG=v8:1854
TEST=existing tests in mjsunit
R=vegorov@chromium.org

[ulan, 2012-04-26 13:19:09]

Could you please take a look? This is one of Steven's open CLs.

[Vyacheslav Egorov (Chromium), 2012-04-26 13:37:59]

LGTM if we have good test coverage that will verify the cases when caching is
valid and invalid.

also different interesting cases:

var a = 10;
eval("a");
with ({a:11}) { eval("a"); } 

and similiar.