Introduce batching of eager loads

During hydration when an association is encountered that is configured EAGER this entity is directly loaded through a separate SQL statement. This is inefficient for single-valued associations as it leads to the n+1 queries problem. This should be improved by somehow collecting all entities that need to be eagerly fetched and loading them in a single statement or in batches.