Fix the caching for mergeability framework

What does this MR do and why?

We originally investigated the usage of adding caching to the approved service mergability checks. The caching of this check was too difficult with the cache invalidation, and it was not going to be beneficial. During the investigation I noticed that the caching framework (which is currently not used) has a few issues with using it, primarily around after getting the data from the cache. So in this MR we are fixing this when we pull the data from the cache.

Related to #377310 (closed)