Currently OptimizeObjectMapperProvider is used for both the optimize Rest api + the engine client. Further the provider currently creates a new mapper everytime it's called, it could just cache the mapper once.

AT:

• the engine client uses a dedicated engine mapper
• the rest api uses the optimizeMapper
• mappers are not recreated for each call to *ContextResolvers