Add Resolver for MaplessReference about mapless HOT 2 CLOSED

@eMaringolo I like the idea of leaving room to plug different strategies to do that. And yes, at this point it will create proxies to references but only query for its document lazily with the DNU when they receive some message.

If we add a MaplessReferenceResolver I'm thinking in two questions:

1. The model identity and
2. the proxied model identity

Whatever it is going to do, it has to maintain that consistent in one cache.

One approach I'm thinking right now, is to use the dynamic variable MaplessCurrentRepository to hold the lifespan of that cached object in a way that can be thread-safe without requiring further complexity. If we use that, the name of that dynamic variable might change to something that isn't a transaction but starts to feel like one.

If you have suggestions, feedback or further input to consider I'd like to hear.

from mapless.

Done here #48

Thanks again @eMaringolo

from mapless.