Update/Install-time service overrides for cache should support MemoryCacheInterface

Problem/Motivation

In #3047289: Standardize how we implement in-memory caches, I fixed kernel tests to support services so they can use MemoryCacheInterface. I think that makes sense, because if a service specifically wants a memory cache for performance reasons, it should use that type.

However, in #3037156: Modernize locale history functions, we did run into a lot of installer test fails when trying to do that with a locale service that's used early in the installer. The reason is that \Drupal\Core\Installer\NormalInstallerServiceProvider::register contains the same brute-force cache factory override. I think it should use the approach from \Drupal\KernelTests\KernelTestBase::register() and I verified it works.

But there's also UpdateServiceProvider, which uses \Drupal\Core\Update\UpdateCacheBackendFactory, which uses a decorator, that would need a different decorator or we just always also implement MemoryCacheInterface there. I'm unsure the existing update tests aren't failing on that.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet