Add CodeActions to resolve syntax errors related to sections

[JessicaJHee]

Fixes #821

[JessicaJHee]

Currently for the UNTERMINATED_SECTION code action, I insert the section end tag after any child content. I'm not sure if this is this best approach or the end tag should be generated fight after the start tag.

This is the current behavior:

[angelozerr]

@JessicaJHee your PR looks very good.

I would like to merge my PR #832 before yours and as I did some refactoring you will need to change your code (JavaDataModelCache has changed and now code action uses QuteProjectRegistry instead). The resolveJavaType is done with project and not with java data model cache.

[angelozerr]

I think you could add case SECTION_BLOCK_END_DOES_NOT_MATCH_START here (no tested)

[JessicaJHee]

In this case I should correct the end tag to {/else} or {/if}?

It seems like the following case is allowed since I get no errors when I build Quarkus:

{#if true}
    Hello
    {#else}
    Hi
    {/else} // --> error is reported here - I have added a test case for this
{/if}

But at the moment we report error since we declare {#else}, {#case}, and {#is} as empty sections here:

quarkus-ls/qute.ls/com.redhat.qute.ls/src/main/java/com/redhat/qute/parser/template/TemplateParser.java

Line 352 in 0726aa5

return CaseSection.TAG.equals(tag) || ElseSection.TAG.equals(tag) || IsSection.TAG.equals(tag);

[angelozerr]

Ok thanks for your feedback. It is more complicated that I though. We can do that in a separate PR. Please create an issue for that.

[JessicaJHee]

I have created an issue here: #844

[angelozerr]

@JessicaJHee please fix conflict

[angelozerr]

I love your work @JessicaJHee, thanks so much!