Fix current field not updating after pasting value

[Rindbee]

Reverts #76711 and supersedes #76711.
Fixes #75124, fixes #78578.

This commit only updates the field that is currently affected.

[akien-mga]

Looks safer for sure.

[akien-mga]

CC @ajreckof

[akien-mga]

Reverts #76711 and supersedes #76711.

Did you mean to link #78591 as superseded?

[Rindbee]

Did you mean to link #78591 as superseded?

I'm not sure, #78590 doesn't seem to be a regression of #76711.

[ajreckof]

This will not supersede #78591 As this does not fix #78590 but #78591 will in fact supersede this.

I'm not sure about the way to update the property here as it will not fix the inconsistency with other places where calling emit changed with p_changing = false will trigger an property update

You could on the other hand call update property from the emit_changed callback but only the property needed. This would need to store esitor properties but shouldn't be too hard.

Edit : I just realised this PR does not fix the first issue (neither does my suggestion) as it won't work when type has changed because each editor property can only handle one type and therefore it can't show the new value since it has an invalid type. This might even create errors or crash when updating the property will require the correct type

Doesn't seem as safe as I initially thought, as it actually will update in more cases when pasting.

[Rindbee]

For some cases in Array, updating the parent's EditorProperty seems to be a must. It may be necessary to distinguish between typing and pasting.

[ajreckof]

I think the proper solution to avoid too much update is to rework update_property to be a bit more intelligent and only destroy/recreate that do need because they were either added removed or type changed. But I feel like this is something that can wait for 4.2

[Rindbee]

It is impossible to solve the case where a value of a different type is copied to an element of Array to change the element type.