[Inconsistency] Filtered transclusion syntax does not assign attributes to rendered HTML output about tiddlywiki5

[Jermolene]

Hi @pmario in these situations I think it's clearer to add the tests in with the PR that includes the fix

[pmario]

The unused "tooltip" construction {{{ [tag[docs]] |tooltip||TemplateTitle}}} is inconsistent with transclusion parameters, because the order is different.

To be able to cleanly fix bug-#7701 I do suggest, that we completely remove the unused regexp and the unused code.

So we will be able to add stuff back if we should need it in the future.

@Jermolene -- I do need a decision about this one to be able to fix #7701. To be able to fix #7701 in a clean way we need at least remove match-group 4, the "style" section

[Jermolene]

Hi @pmario I would be inclined to agree that we should completely removed the unused parts of the regex and the associated code.

[pmario]

@Jermolene ... I did add 4 new tests for filtered transclusions "inline" and "block" mode.

• All tests pass with the new code.
• 1 test fails with current master branch.

So should I include the test with the PR that fixes issues #7701 and #7797

or

Should I create a separated PR that only contains the tests.

-> The problem will be, that the vercel CI will fail those tests

[pmario]

@Jermolene -- bump -- info needed

[pmario]

The latest proposal from Jeremy is at: #7822 (comment)

Which can be changed to the following format, which gives us even more future possibilities.

vars ... can be any text except | -- even linebreaks are possible
params ... similar to vars but with basically no limitations

{{{ [tag[docs]] }}}
{{{ [tag[docs]] | vars }}}
{{{ [tag[docs]] || TemplateTitle }}}
{{{ [tag[docs]] | vars || TemplateTitle }}}

{{{ [tag[docs]] }} params }
{{{ [tag[docs]] }} param:"value" | another="value" }

{{{ [tag[docs]] }} param:"value" | another="value" | any text we want 
including line-breaks }