Set maximum default cache sizes to avoid cache OOMing the service

While testing profile, Zach and I noticed that while initial cache capacity is set, we never set a maximum. This could cause issues where the cache completely fills the containers, or grows to an unmanageable size. To combat this, we should set a default limit of 10k entries, which should be enough for most of our use cases. Any other cases, we can just override those build properties in the downstream applications easily.