Change used interface to FieldableEntityInterface where it makes sense
Problem/Motivation
Some places strictly rely on ContentEntityInterface implementations, whereas when solely accessing field-related stuff it makes sense to make use of FieldableEntityInterface instead.
This issue is a refactor which should prevent from wrong usages, e.g. FieldUpdateActionBase asserts for EntityBase but it needs to assert for a FieldableEntityInterface instead.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Edited by drupalbot