Issue #250: Implements Bidirectional RelationshipResolver

The goal of this PullRequest is to prevent any scenarios that could potentially cause relationships not-to-be-sync'ed, such as "Source Objects" being inserted after the "Target Objects".

The new mechanism will store a descriptor for each relationship, containing the following fields:
- **Source Object:** Key, bucket and attribute
- **Target Object:** Key + bucket**

Whenever any of the involved objects get inserted (Source/Target), the relationship resolver will check the pending descriptors containing the inserted object's key, and will attempt to establish the relationship. This will be performed for both, Source + Target objects. As a result, insertion order should not be an issue anymore.

Fixes Issue #250 

Is it OK to use `entityName` as the bucket name now? We used to have some potential remapping e.g. for unit tests, but not sure about the status of that.