Improve handling on level of typed data in DTO and Configuration
Problem/Motivation
We provide a DTO data type that is supposed to handle any sort of data properties, as long as it's passed to it as typed data. This brings the theoretical benefit of having an object holding different field item lists (and configuration values) without losing its parent information, i.e. one DTO may hold multiple properties coming from different sources.
While already working fine for content entities, it is not yet working well for configuration entities and objects. But there is a manager for typed configurations, so a DTO should be capable of handling configuration data in the same manner as it's already doing for content entity fields.
Steps to reproduce
Proposed resolution
Remaining tasks
Make this behavior consistent regarding content as well as configuration. Once this is fixed, we are able to use DTOs for various use cases, e.g. for building custom forms.