Adding compatibility with symfony/expression-language

Adding the ability to process string expressions using the
symfony/expression-language. It keeps backward compatibility to the
provided operators and with any new operator defined using the default
mechanism.

One upside down with this approach is that you can have a full object
inside the context and evaluate on its attributes using a symfony
expression.
In this case it will be wise to throw a new exception or simple return `false` by default? In my use case defaulting to `false` will be enough, but I'm asking for a more general opinion.