Take advantage of the LibraryManager.enableCaching feature

[brynrhodes]

The Language Server currently implements a NonCachingLibraryManager to avoid caching libraries in the LibraryManager. To avoid the need to subclass, an option is being added to the base LibraryManager (cqframework/clinical_quality_language#667). Once this issue is complete, remove the NonCachingLibraryManager class from the language server and just set the option instead.

[JPercival]

I actually think we do want to cache in the interest of maximal language server performance. The noncaching behavior is a hackaround for not being able to expire the library cache on a per library basis. So, I'd argue that the caching option is not the optimal solution for this. Rather, we need an API that allows us to control the Library cache on a more granular basis.