Drupal Core 8.7 compability

Problem / Motivation

I digged in the database to verify if the cache exclude settings work. And surprisingly they didn't.
My (custom) entities always got cached. Also I the tests for this module fail, when running against 8.7.

Proposed solution

My investigations lead me to the fact that the persistent_cache setting was not changed anymore, in the storage controller.
And then I found this issue: #2554235: Make the content entity storage and entity query use the last installed definitions instead of the ones living in code

Quickfix

This led me to also change the Active Definition in field_encrypt_entity_type_alter, which made it work again.

Conceptually I think the code from hook_entit_preprocess should be executed, when config is saved, in the already existing config listener. IMO static cache can also be removed, or exposed as (super secure) setting, see also: #3073924: Improve how the effects on cacheability are controlled

Open questions

• Maybe a more generic way needs to be provided by core (probably other modules implementing hook_entity_type_alter will fail too).
• Unsure about the field manager definition, do they need to be updated too?
• Is the try/catch block enough to ensure backwards compability?