[Bug]: MergePatchUpdate graph representation not ideal

[bterlson]

When you look at the graph, the body references the MergePatchUpdate, but its properties' .model reference the mutated model with the proper name. Emitters must take care to apply friendlyName at least, but you also need to be careful to avoid duplicate types if you end up with the actual mutated model somewhere. In my emitter I have fixed this by normalizing the MergePatchUpdate graph node to the first property's .model.

[markcowl]

I think this is an artifact of using the decorator to mutate the modelProperties - I wonder if replacing the model template that uses a decorator with a function is the most natural solution.

[timotheeguerin]

I think this is something that should be resolved when we have the functions, the template model can be replaced with a template function and that will work