OGM-338 Renaming MappingContext into OptionsContext
OGM-338 Establishing API for accessing provider-specific, typed GlobalContexts via OgmSession
OGM-338 Splitting up OptionsContext into a context keeping track of the entities/properties configured in one invocation of the fluent API and a shared context which keeps track of all configured options per SessionFactory/Session
OGM-338 Renaming base context types to be more consistent
OGM-338 Reading annotation-based options lazily
OGM-338 Simplifying AnnotationProcessor
OGM-338 Removing indirection of MappingFactory, having DatastoreProvider itself return the typed global context instead
OGM-337 Avoiding repeated creation of OptionServiceContext objects by having OptionContext implement OptionServiceContext directly
OGM-348 Adding API on OptionsContainer to access options in a type-safe way