Entity view and form display configs might still depend on the old field name on some occasions

Problem/Motivation

Currently, some configs of the enitty view / form displays, might still depend on the old field names after renaming the field. We should see that all occasions of the old field name are converted to the new one.

Steps to reproduce

Proposed resolution

Go through the view / form display config and check every key and value for the old field name. If it exists, we should replace it. NOTE, that this approach might lead to similiar field names also being overriden, we need to think about this properly.

Remaining tasks

User interface changes

API changes

Data model changes