feat: Binding expression parser additions and improvements - #9791

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/DevelopmentWorkflow.md#running-unit-tests-application.
• Tests for the changes are included - https://github.com/NativeScript/NativeScript/blob/master/tools/notes/WritingUnitTests.md.

What is the new behavior?

The follow additions are included in this patch:

• Better error reporting for binding expression parsing failure
• Added missing optional chaining support for callbacks
• Using a safer approach to recognize converters
• Fixed an issue that caused a circular reference for $value key in certain cases of two-way binding
• Re-added lost converters feature according to docs: Since the usual operation is converting data from model to view, if a function is provided as converter, it acts as a toView function.
• If a property caller is undefined (e.g. caller.property1.property2), parser will return undefined instead of throwing error. This is similar to old behaviour and is an attempt to fix issues similar to core 8.2.0-alpha.1+ : Binding: Run-time error occured in file: undefined at line: undefined and column: undefined #9785

@felixkrautschuk This patch includes changes that should help with your issues. Once this is merged in an alpha version, I would like you to give me some feedback regarding its functionality.

Fixes #9785 .