Cosmos: Container Metadata Cache

[analogrelay]

This PR adds an initial version of the Container Metadata Cache, which caches metadata about a container that is frequently needed but infrequently changes. Right now, that's limited to the RID, but the patterns are here to allow us to add more cached metadata as needed.

To create an async single-flight (defined shortly) cache, I decided to use a third-party crate rather than building it myself. I did start along the path of building it myself and we can certainly do so, but as I got into testing I realized that I'd much rather use something well-tested that already exists for now. I chose the top result on crates.io when looking for an async cache: moka, which crates.io itself uses. It is frequently updated and highly used in the ecosystem. Plus, we don't expose anything from it on our public API, so we can replace it later without risk to users.

The main reason the cache is complicated is that I really wanted to make sure the cache was both async-friendly (i.e. works with async/await) and "single-flight", meaning there's only ever one outstanding request to update a given cache key. Those familiar with .NET might think about Lazy<T>'s "LazyThreadSafeMode". A single-flight cache is similar to LazyThreadSafeMode.ExecutionAndPublication, in that it ensures that only a single initialization function is running at a time. Moka does this, via get_with (we actually use get_with_by_ref, but it's very similar), which guarantees:

... that concurrent calls on the same not-existing key are coalesced into one evaluation of the init future. Only one of the calls evaluates its future, and other calls wait for that future to resolve.

https://docs.rs/moka/0.12.11/moka/future/struct.Cache.html#method.get_with

Not all of our SDKs do this kind of optimization, but I believe the .NET one does (from my reading) and if the Rust SDK is to serve as a core reference implementation, it seems important for it to do it as well.

Building an async single-flight cache in a runtime-agnostic way (i.e. not directly depending on tokio, smol, or some other async runtime) is possible, but complicated, so I wanted to let Moka do all that work for us for now ;).

[analogrelay]

Azure/azure-sdk-assets@69ad1e4#diff-7879243660aeae990c47455256d1e25f7fe7ed0e8f9206a047e4eb054849ecd0

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

azure_data_cosmos