XMLports: Typing (but not pasting) properties like TransactionType, TextEncoding produces spurious warning that "'schema' cannot be used in this context"

equivalent to #6225 but for XMLports instead of Reports.

Describe the bug
Typing TransactionType = [whatever]; creates a spurious error about schema not being valid/expected. The same goes for TextEncoding and possibly others. I didn't check more: this is simply a bug that needs to be fixed at the source, for all properties.

To Reproduce
Steps and to reproduce the behavior:

1. Create an XMLport
2. Put an schema{} in it
3. Go up to and type a TransactionType = Update; (e.g.) before the schema, in the object properties area.

Interestingly, I can then cut and paste that line with the vim keybindings, and the error goes away (a) when it's cut obviously and (b) even after it's pasted back in the same form.

I also do not see this error when I type e.g. TransactionType=Update; i.e. without spaces and the auto-formatted runs and puts the missing spaces in; that's OK.

Expected behavior
This is not an error, as the ability to cut and paste the same code and get no error proves... so it should never be (sometimes) reported as one!

Screenshots

after adding the line by typing it:

after cut/paste:

5. Versions:

• AL Language: 6.1.352568
• Business Central: n/a but latest 16.x dev sandbox

Start by reproducing the issue in an AL XMLport containing schema{} and type TransactionType = Update; before the schema in the object properties area. Compare the diagnostics produced while typing the property with those produced after cutting and pasting it, including the spaced and unspaced forms. Done means valid XMLport properties no longer produce the spurious "schema" warning.