Update/UpdateById and Set/SetById don't honor newly defined filterable properties

[davidLeonardi]

Defining new filterable properties on a model while performing update/set operations does not result in the creation of filterable properties in the actual datamodel.
This only occurs in .push() but should also occur in .update() or .set() as we might be introducing new values/properties.

For example, assuming the following code:
const users = modelDenormalizer('users'); users.filterableProperty('photo'); return users.updateById(${uid}, {photo})
Will not result into a lookup table called photoUsers, but will if i use push().

[davidLeonardi]

davidLeonardi@25e8304 to see what i did for update