Allow skipping translation check at field level for non-translatable fields

Problem/Motivation

To support draft revisions for content with paragraph fields we faced issues as mentioned #2956311 🐛 Error when save translation Closed: duplicate

We followed all the steps as mentioned in documentation → and then faced the issue as further detailed out in #2956311#14 🐛 Error when save translation Closed: duplicate

Proposed resolution

Approach behind making paragraphs translatable without making field translatable seems to be not compatible enough with the validations for translatable field changes in CORE. There were some additions already done to CORE to make things work, we need to add one more change in CORE to allow skipping validation for untranslatable field changes for paragraph fields.

We can add a new setting at field level to allow skipping them and then use it like computed fields check to skip them during validation. We used this in our project and it made everything work - we are now able to create draft revisions