Avoid unnecessary use of FieldPath inside ExpressionObject

Inside ExpressionObject::evaluateInternal() we use MutableDocument::setNestedField() and a FieldPath, perhaps to handle dotted paths? But when parsing we assert the field names do not contain dots. We should use MutableDocument::addField() and stick with the string for both performance and clarity.