I've missed this during https://issues.ibexa.co/browse/IBX-7827 tests, so im reporting this as separate core bug.

Prerequistes:
Ive attached migration yaml file with content type, which has 2 fields, one with Translatable parameter and the other one without Translatable parameter

Steps to reproduce:
1. Migrate the attached file (https://doc.ibexa.co/en/latest/content_management/data_migration/importing_data/)
2. Go to Content/Content Types
3. Edit added content type

Actual result:
'textline24' field has Translatable parameter set to true, even though it was undefined in the migration.

Expected result:
Migration should not force parameter as true if it is undefined in migration yaml.