ProtobufMatcherEvalContext should also fire missing properties

Not doing so leads to 'is null' predicates not being evaluated precisely because the property is null, which leads to an incorrect match result. This issue does not happen in the reflection based case.

Missing properties should be fired with their default value if they have one, otherwise with null, unless their type is not nullable in which case nothing needs to be done for them.