Consider the following case:
- Article A
- Article B
- Article C
- User X has write access on B, but read access on C.
-> User X moves B so that it is now a sibling of A.
-> Since C is a child of B, it also underwent a change, which is caused by X.
To clarify this situation and the fact that X does not have write access on C, the
automatic field tracking message is made more explicit in this case (Changes of
C are a side effect of the changes of B).
Task-2858428
X-original-commit: e6af7c8c6a2eb37038742ce93018a8eb8cfbf6d6
Part-of: odoo/odoo#93088