Add a way to configure caches Jackson uses

[cowtowncoder]

(note: follow up on #2456 )

Currently most of caching Jackson does internally (for reusing things like serializers, deserializers, to avoid re-resolving some generic types and so on) is internally defined with settings that can not be changed. But it would make sense to expose an interface, like cache provider, that could be changed to override either some parameters (sizes for default caches) or even cache implementations if that matters. This would also allow things like instrumentation (for cache hit rates) and using time-based eviction, dynamic sizing and so on.

Known caches are in:

• DeserializerCache (added via Add a way to configure DeserializerCache Jackson uses #4101)
• SerializerCache (added via Add a way to configureSerializerCache Jackson uses #4111)
• TypeFactory (added via Add a way to configure TypeFactory Jackson uses #4115)
• RootNameLookup (small -- probably no need to configure)
• JacksonAnnotationIntrospector (_annotationsInside) -- (tiny, likely no need to configure either)

Some modules may add their own caches as well although not many do; and so configuration of those can be separate from databind.

[cowtowncoder]

Marking as "most-wanted" as this tends to come up occasionally, esp. wrt Scala module.

[pjfanning]

If there is a rewrite of LRUMap, maybe ConcurrentLinkedHashMap could be copied into jackson-databind. LRUMap is currently based on ConcurrentHashMap but ConcurrentLinkedHashMap allows for an eviction policy that would allow one in, one out semantics once maxEntries is reached.

[cowtowncoder]

Merged #3531 (improve LRUMap impl not to clear all entries on max size) which is related but not necessarily 100% what this is so leaving open.

Also implemented #3311 (add serializer cache limits in 2.14).

These should make it easier to work on this one.

@pjfanning Now that both SerializerCache and DeserializerCache (see #1905) use New and Improved LRUMap, it might be possible to work on this. I think we'd need a new config object to be passed via ObjectMapper.builder() but should be doable for 2.x not just 3.0. Might not make it in 2.14 due to timing, but at least closer to being doable.