Config entities that have IDs which are built from other properties should update those properties when the ID changes

Problem/Motivation

#3481695: Entity displays cloning requires special config action extended the cloneAs config action to allow stuff like this:

core.entity_view_display.node.page.default:
  cloneAs: node.blog.full

In that issue, we modified EntityDisplayBase::set() so that, if the entity's ID is changed, the other properties which are derived from that ID (or, rather, used to build the ID) are updated too.

The problem is, we only did that for entity displays. There are other config entities that follow a similar pattern, where the ID relates to other properties in a meaningful way -- fields and their storages leap to mind. We should maybe generalize the logic of entity view displays so that it works for all config entities that are structured like that.