Remove bogus flags from call-counts.js test.

Remove bogus flags from call-counts.js test.

The runtime flag in question makes no sense, because the feature cannot
be disabled without keeping the snapshot in sync. We should avoid having
the flag in our "mjsunit" test suite, so that CluserFuzz doesn't pick it
up. The test in question is already skipped, the change will not affect
test results on our waterfall.

R=mvstanton@chromium.org
TEST=mjsunit/call-counts
BUG=v8:4458
LOG=n

Committed: https://crrev.com/2aba89e3362f1ab435b3041ea67b442cf258f9b1
Cr-Commit-Position: refs/heads/master@{#31302}

[mvstanton, 2015-10-15 12:31:17]

lgtm, thanks!

[Michael Starzinger, 2015-10-15 12:34:29]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2015-10-15 12:34:42]

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

[commit-bot: I haz the power, 2015-10-15 13:31:42]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-10-15 13:32:08]

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