EZP-19884 Refactoring content object storage and update

This PR implementes EZP-19884 Refactoring content object storage and update

Content service now no longer passes complete set of fields to storage.
When creating content fields that are not set in create struct are not passed. When updating content with new language, fields for new language that are not set and untranslatable fields are not passed. Storing these fields is now handled inside legacy storage. This enables future storage engines to avoid redundant storage.

Updated:
FieldType configuration is injected into persistence handlers through constructor. Symfony's LegacyStorageEnginePass is updated to account for that.
When creating Content for untranslatable fields only field in main language is passed to persistence.

Note: on updating with new language ContentService still validates complete set of fields against ContentType - meaning validating non-translatable fields that are not passed to the persistence, but instead copied there from field in main language.

TODO:
- [x] Integrate Persistence FieldType when #205 is pulled in