BREAKING CHANGE: Allow explicit code callout only after a comment

[reakaleek]

Changes

Only allow explicit code callouts after a comment # or //.

This way we avoid cases where there are valid angle brackets in the code.

Related Issues

• Codeblocks with valid use of angular brackets mistaken for callout #431

[Copilot]

PR Overview

This PR implements a breaking change that restricts explicit code callouts so that they are only recognized when preceded by a comment (either "#" or "//"). The changes update documentation, adjust parser logic in the Markdown parser, revise corresponding tests, and update the docs navigation to include the new code callouts page.

Reviewed Changes

File	Description
docs/testing/code-callouts.md	Added examples illustrating code callouts with preceding comments
src/Elastic.Markdown/Myst/CodeBlocks/EnhancedCodeBlockParser.cs	Modified parsing logic to only consider callouts after a comment marker
docs/syntax/code.md	Updated instructions and examples to reflect the new requirement for explicit callouts
docs/_docset.yml	Added the code-callouts documentation page to the docset
tests/Elastic.Markdown.Tests/CodeBlocks/CallOutTests.cs	Updated test cases to include the required comment prefix for callouts

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

tests/Elastic.Markdown.Tests/CodeBlocks/CallOutTests.cs:154

• [nitpick] The class name 'ClassicCallOutsFollowedByListWithWrongCoung' contains a typo; consider renaming it to 'ClassicCallOutsFollowedByListWithWrongCount'.

public class ClassicCallOutsFollowedByListWithWrongCoung(ITestOutputHelper output) : CodeBlockCallOutTests(output, "csharp", 

[Mpdreamz]

I think it's best if we inverse the logic here, instead of breaking all the existing code blocks, require those that want to keep the <\d+> at the end of a string to prefix it with \ e.g \<1>.

That way it still works as its always done for the vast majority of cases.