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?

When using the fenced-code-language rule, the endColumn error location is reported incorrectly in the 'What did you expect to happen' example below:

What did you expect to happen?

First Problem

I expected the error location to end at the last backtick or tilde character, but it extends endlessly when there are spaces after the backtick or tilde.

• Result

• Configuration

<!-- eslint markdown/fenced-code-language: "error" -->

• Source Code

```                                                                                                           
console.log("Hello, world!");
```

Second Problem

I expected the endColumn error location to be 17, but it reports 20, which exceeds the actual line length.

• Result

• Configuration

<!-- eslint markdown/fenced-code-language: ["error", { required: ["js"] }] -->

• Source Code (The code below creates a valid Code node: AST)

   ```javascript
console.log("Hello, world!");
```

The following error location would help identify the problem:

{
    messageId: "disallowedLanguage",
    data: { lang: "javascript" },
    line: 1,
    column: 4,
    endLine: 1,
+   endColumn: 17,
-   endColumn: 20,
},

Link to minimal reproducible Example

Adding the following test cases to the invalid tests in tests/rules/fenced-code-language.test.js causes the tests to fail due to incorrect error reporting location.

First Problem

		{
			code: "```     \nconsole.log('Hello, world!');\n```",
			errors: [
				{
					messageId: "missingLanguage",
					line: 1,
					column: 1,
					endLine: 1,
					endColumn: 4,
				},
			],
		},

Second Problem

		{
			code: `   \`\`\`javascript
console.log("Hello, world!");
\`\`\``,
			options: [{ required: ["js"] }],
			errors: [
				{
					messageId: "disallowedLanguage",
					data: { lang: "javascript" },
					line: 1,
					column: 4,
					endLine: 1,
					endColumn: 17,
				},
			],
		},

What changes did you make? (Give an overview)

I've updated the rule so it reports the error location correctly.

Also, I've added test cases.

Related Issues

N/A

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

N/A