Use L1/L2 caching strategy for application_settings

Right now application_settings only is cached in a thread-local memory cache. We've seen in production incidents that a significant number of packets are being consumed with loading these from the database.

We should use an L1/L2 cache approach here as well, as we do with feature flags.