fix: Event binding in XML Templates

[d3xter666]

In XML templating it's possible to provide bindings fоr every attribute no matter if it's property, aggregation, event, etc.
Therefore, the linter needs to analyze the bindings within events as "normal" bindings and not just like events.

[matz3]

Can you also add a fixture for the class attribute? That one is also used in XML templating e.g. class="{=${device>/system/phone} ? sapMObjectStatusSmall : sapMObjectStatusLarge}"

[matz3]

A composite binding is a valid binding but doesn't necessarily start or end with curly brackets, e.g. .event{field>Value/$Path}Handler.

AFAICS the bindingInfo will not be an object if there is no binding, so it is already sufficient to check for that.

Also see my changes in #533 which set the bUnescape argument to false.

[d3xter666]

Please, check the new solution. It verifies if the potential function name is a valid JS identifier.
The pattern is a bit enhanced to support the all the variants of using functions in XML.
Source:

ui5-linter/src/linter/html/transpiler.ts

Line 329 in 3abcf56

const validFunctionName = /^[$_\p{ID_Start}][$_\p{ID_Continue}]*$/u;

[matz3]

Please add new cases which previously caused false-positive findings to test/fixtures/linter/rules/NoGlobals/GlobalEventHandlers.view.xml.

[matz3]

There seem to be problems with parsing certain bindings which are working fine at runtime, but can't be parsed in here:
<Button press=".onPressButton($event, { code: ${ui>/sCode} })" />

This causes a parsing error Unexpected '$'.