Update: report backtick loc in no-unexpected-multiline (refs #12334)

[mdjermanovic]

Prerequisites checklist

• I have read the contributing guidelines.
• The team has reached consensus on the changes proposed in this pull request. If not, I understand that the evaluation process will begin with this pull request and won't be merged until the team has reached consensus.

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

[X] Other, please explain:

refs #12334

Change reported location in the no-unexpected-multiline rule.

For tagged template literals, this change can produce more warnings in existing code, depending on the location of eslint-disable-* comments.

What changes did you make? (Give an overview)

• Tagged template literals: rule will now report template literal's backtick location, instead of tag's start location. This is consistent with other node types.
• All other nodes: rule will now report the full location of (, [, /, instead of just their start locations.

Before:

After:

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

An existing code like the following will have a no-unexpected-multiline error after this change:

/* eslint no-unexpected-multiline: ["error"] */

// eslint-disable-next-line no-unexpected-multiline
a
`b`

Other changes:

• data isn't used in error messages, so it's removed.
• if (node.tag.loc.end.line === node.quasi.loc.start.line) conditional was redundant, so it's removed.
• Formatting for the last test case (tagged-template-with-generic-and-comment) was wrong, so it's fixed to match the actual input (which is observable from the reported location).

[kaicataldo]

👍 for better consistency in the error report location. LGTM, thanks!

[yeonjuan]

LGTM! Thanks

[kaicataldo]

Thanks for contributing!