Bidirectional association management shouldn't ignore maintaining inverse lazy objects
Description
As part of https://hibernate.atlassian.net/browse/HHH-15602 I implemented an optimization that avoid lazy initialization of the inverse bidirectional association, because I thought the auto-flushing would kick in before lazy loading a collection/proxy. We figured in https://hibernate.atlassian.net/browse/HHH-10445 that this is not the case, nor is it correct according to our documentation.
Therefore, this lazy object optimization has to be removed in order for bidirectional association management to work properly.
As part of https://hibernate.atlassian.net/browse/HHH-15602 I implemented an optimization that avoid lazy initialization of the inverse bidirectional association, because I thought the auto-flushing would kick in before lazy loading a collection/proxy. We figured in https://hibernate.atlassian.net/browse/HHH-10445 that this is not the case, nor is it correct according to our documentation.
Therefore, this lazy object optimization has to be removed in order for bidirectional association management to work properly.