Tests and fixes for (pre)parse errors related to strict reserved words.

Tests and fixes for (pre)parse errors related to strict reserved words.

This contains the following fixes:

- We had strict_reserved_word and unexpected_strict_reserved, which one to use
was totally mixed in Parser and PreParser. Removed strict_reserved_word.
- When we saw a strict future reserved word when expecting something completely
different (such as "(" in "function foo interface"), Parser reports unexpected
identifier, whereas PreParser used to report unexpected strict reserved
word. Fixed PreParser to report unexpected identifier too.
- Unified parser and preparser error locations when the name of a function is a
strict reserved word. Now both point to the name.

BUG=3126
LOG=N
R=ulan@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=19067

[marja, 2014-02-04 12:07:18]

ulan, ptal

[ulan, 2014-02-04 12:14:42]

lgtm

[marja, 2014-02-04 12:20:02]

Committed patchset #1 manually as r19067 (presubmit successful).