fix: wrong location reporting in no-invalid-label-refs

[lumirlumir]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

Which language are you using?

CommonMark and GFM.

What did you do?

The error location reported by no-invalid-label-refs is correct for single-line text, but in multi-line text, it's one index(offset) behind where I expect.

What did you expect to happen?

I expected the error location to begin at [ and end at ], but in multi-line text the end column is one index behind.

Link to minimal reproducible Example

Adding the following test case to the invalid section would help identify the problem.

		{
			code: "[\nfoo\n][\n]\n\n[foo]: http://bar.com/image.jpg",
			errors: [
				{
					messageId: "invalidLabelRef",
					data: { label: "foo" },
					line: 3,
					column: 2,
					endLine: 4,
					endColumn: 2,
				},
			],
		},

Originally, the endColumn was 1, but it needs to be 2 so it includes ] as it does for single-line text.

What changes did you make? (Give an overview)

In this PR, I've fixed wrong location reporting in no-invalid-label-refs.

Related Issues

N/A

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

N/A

[lumirlumir]

The following example was correct code, so I've updated it to show incorrect code.

(I've also added a test for it.)

[eslint][

]

[lumirlumir]

The column is a 1-indexed value, so it needs to be 1, not 0.

markdown/src/language/markdown-language.js

Lines 118 to 122 in bae7da7

	/**
	* The column number at which the parser starts counting.
	* @type {0|1}
	*/
	columnStart = 1;

[mdjermanovic]

LGTM, thanks!