WIP. Done.

• Request: give token types and etc to plugins acornjs/acorn#870 acorn introduces a new mechanism that plugins access the actually applied acorn entity.
• update to use Parser.acorn acornjs/acorn-jsx#102 acorn-jsx plugin uses the mechanism.
• Fix: misuse token types (fixes #393, refs eslint/eslint#11018) js#426 espree plugin uses the mechanism.
• release a new espree.
• (this PR) eslint uses the updated espree.

What is the purpose of this pull request? (put an "X" next to item)

[X] Bug fix: #11018

What changes did you make? (Give an overview)

This PR fixes #11018 as using the new mechanism that acorn plugins can access the actually applied acorn entity.

The problem has happened when the two acorns are different entities.

1. The acorn that is using plugins.
2. The acorn that the plugins imported by require("acorn").

After this PR, acorn plugins get to not use require("acorn").

Is there anything you'd like reviewers to focus on?

I'm not sure how I add tests.

You can confirm that this PR fixes the problem:

1. Install eslint, espree@6.1.1 and acorn@6 (espree@6.1.2 has been fixed this problem)

   npm install acorn@6.x espree@6.1.1 eslint
   

2. Check node_modules has the following structure.

   node_modules/
   ├ acorn/ (6.x)
   ├ acorn-jsx/
   └ espree/ (6.1.1)
     └ node_modules/
       └ acorn/ (7.x)
   

3. Lint a file that contains JSX syntax. (expected a syntax error of the problem)
4. Install the latest espree.

   npm install espree@latest
   

5. Lint a file that contains JSX syntax. (expected no errors)