CacheContext() writeFn should write emitted events as well

[colin-axner]

Summary

Calling context.CacheContext() and then writing the cacheContext should emit the events from the cached context as well

Problem Definition

Calling cache context followed by writeCache() does not emit the events emitted for the cached context since a new event manager has been used for the cached context. This causes the caller to also manually emit the events

Proposal

Modify the existing context.CacheContext() function to return a writeCache() function which also emits the cached events into the actual context event manager

[ValarDragon]

This is a bug that would be really helpful if fixed. caused a bug with events in Osmosis & persistence that @puneet2019 fixed for us.

[yihuang]

yeah, caller site has been writing the events explicitly, not sure if there's use case that don't want to write the events, maybe add a boolean parameter to the write function?