Update: reporting loc for never option in eol-last (refs #12334)

[snitin315]

Prerequisites checklist

• I have read the contributing guidelines.

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

[x] Other, please explain:

What changes did you make? (Give an overview)

Refs #12334

Add assertions on reporting location in test cases for eol-last.

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

No

[mdjermanovic]

I think it's fine for "always" to report only start loc after the code, but for "never" we could report the linebreak's range (VSCode handles this well by underlining space after the column end) like we are already doing in the linebreak-style rule. Thoughts?

[snitin315]

Makes sense, I will update 👍🏻

[eslint-github-bot]

Hi @snitin315!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The length of the commit message must be less than or equal to 72

Read more about contributing to ESLint here

[eslint-github-bot]

Hi @snitin315!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The length of the commit message must be less than or equal to 72

Read more about contributing to ESLint here

[mdjermanovic]

LGTM, thanks!