modify instances of L<B<... |>...> to B<...>|

[finanalyst]

@thoughtstream The changes in this PR are exclusively related to examples within code blocks with :allow<B>.

After much thought and discussion with @lizmat , and given it will take a considerable refactoring of the parser to allow for both:

A<B<this program |> SOFTWARE>

(of which there are two sets of examples)
and

X<array|B<arrays, definition of>>

I would suggest that we change the specification document (at least temporarily).

Both of the above are examples in the RakuDoc specification.

The first type is the problem. Essentially, the B<> markup has no problem gobbling the |. But then the outer A<> can no longer use the | character to separate the display part from the meta part.

Simply placing the | character outside the scope of the B<> markup resolves the problem completely. The final styling effect is minimal.

The work around in this PR is to copy the whole code block and place inside a comment block for a future revision, and then to modify the B<> markup.

@thoughtstream I am requesting a review since this appears to be the remaining outstanding issue we have.

[thoughtstream]

I'm fine with postponing this capability until the parser can be redesigned
(which, I acknowledge, may mean: indefinitely). It's a small issue and not
one that seems very likely to ever affect the vast majority of users.

[jubilatious1]

What happens to a stray | pipe in a larger Raku script?

[finanalyst]

@jubilatious1 a bit of extra info is needed in order to answer you. In the above examples, though, the code block's HTML goes awry. The error can cascade, or not, depending on the browser. Difficult to test for.