Note blocks and angle brackets incompatibility

[izmalk]

Description

If we use angle brackets inside a note block, even in a code-block, it can break the rendering of the code block.

Environment

1. OS (where TypeDB server runs): 12.6.5
2. TypeDB version (and platform): -
3. TypeDB client: -
4. Other environment details: Jekyll

Reproducible Steps

Steps to create the smallest reproducible scenario:

1. Use the following code in markdown on a page and build the docs.

<div class="note">
[Note]
In versions previous to **2.6.0**, the `--database=` and `--file=` named arguments are not used. 
Use positional arguments instead. For example, `typedb server export <database> <filename>.typedb`.
</div>

Expected Output

Note block is rendered as usual, with a code block in it.

Actual Output

Note block is rendered, but it fails to stop by the </div>. Everything after it is now also a part of the note block.

Additional information

Seems like it sees and/or as HTML tags and waits for their closing tags.

[alexjpwalker]

I was never a big fan of the angle bracket syntax actually, @izmalk . It caused multiple rendering issues due to Jekyll sometimes interpreting them as HTML tags. Let's move towards using braces { } instead?

[izmalk]

Let's move towards using braces { } instead?

I believe there is a known convention (since Unix Man pages) on the syntax. https://stackoverflow.com/a/23242584
I would prefer not to contradict stuff like that to provide the most convenient UX for our users. It shouldn't be a problem with the new docs engine. And with the old one I actually already found a workaround. So I see no reason for abandoning this issue. Maybe not the top priority, but still, should be useful.

And I believe, we already use curly brackets {} for something else in our syntax.