Fix: eqeqeq rule reports incorrect locations

[mdjermanovic]

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

[X] Bug fix

Tell us about your environment

• ESLint Version: 6.3.0
• Node Version: 10.16.0
• npm Version: 6.9.0

What parser (default, Babel-ESLint, etc.) are you using?

default

Please show your full configuration:

Configuration

module.exports = {
  parserOptions: {
    ecmaVersion: 2015,
  }
};

What did you do? Please include the actual source code causing the issue.

Demo link

/* eslint eqeqeq:error */

(a + b) == c;

What did you expect to happen?

1 error with the correct location (column 9)

What actually happened? Please include the actual, raw output from ESLint.

3:7  error  Expected '===' and instead saw '=='  eqeqeq

What changes did you make? (Give an overview)

Changed eqeqeq to find first operator token between, instead of just the first one which could be a paren.

Also, changed the rule to report loc instead of loc.start. One test in cli-engine had to be modified because of that.

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

I hope it's ok to change from loc.start to loc, it always looks better in VS Code.

[mdjermanovic]

Marking as accepted because it's obvious.

[kaicataldo]

LGTM!

[mysticatea]

LGTM, thank you!