Write the foreign keys of has-many and has-one relates in upsertGraph() with noUpdate (#355)

[lehni]

What

With relate and noUpdate, upsertGraph() patches the foreign keys of the models it relates through a HasManyRelation or HasOneRelation. GraphPatchAction adds the relation's related properties of nodes that it relates to the properties it writes, next to the BelongsToOneRelation keys it already collects with noUpdate. The other properties of these models stay unwritten.

Why

noUpdate only skips the property updates, while relate explicitly asks for the relate. The foreign key that the graph sets on the related model was never among the properties to write, so no query ran and upsertGraph() reported success with the model still related to its old owner, or to none. BelongsToOneRelation and ManyToManyRelation relates already write with noUpdate. This has been the case since 1.5.0, where upsertGraph() was rewritten.

Tests

should only write the foreign key when hasManyRelation and hasOneRelation models are related with noUpdate: true relates a model into a HasOneRelation and moves one from another owner into a HasManyRelation, and checks that only the foreign keys change. It fails without the change.

The same fix for 4.0 is in #345. #334 and #336 also add a ## 3.9.1 section to the changelog; whichever merges later combines them.