Compatibility with Organic Group (OG) module

Problem/Motivation

Entity Connect looks not to work perfectly with Organic Group.
We need some more investigations.

Last observations from linked issues bellow:

From mory in #2305037: Fields with GINY 'OG Reference' disappear when returning to parent form →

When returning back to parent form after creating a new entity reference, fields that use the GINY 'OG Reference' disappear.

This makes it impossible to save the form if the field that disappears happens to be mandatory.

To reproduce:

1. Edit any content type and add a field with GINY 'OG Reference', eg. field_og_ref
2. Try to create a new entity on another field of the content type eg. field_custom_entity
3. After saving the new entity and returning to parent form, 'field_og_ref' disappears

Changing the GINY to Checkbox/Select or ay other GINY solves the issue.

However, it'd be nice to use the 'OG Reference' GINY provided by og module in order to benefit from its functionality.

From @brentratliff in #1791130: Organic Groups 7.x-2.x compatability - Selecting OG group content →

This appears to be working with the latest version of OG 2.x with one major exception. You can create a new group but on the redirect the group membership field is no longer on the user profile and it is not automatically referenced if you save the user in that state. It appears that the query string is somehow preventing the group membership field from showing up.
It appears that it's the second half of the query string that's causing the group membership field to drop off the user edit profile.
&return=1#edit-og-user-node
If this is removed from the url, the field works properly after the redirect.