Skip fields provided by "content_translation" when checking for translation changes

When marking the "Flag other translations as outdated" checkbox on default translations, validation is erroneously including the content_translation_outdated field in the list of changed, untranslatable fields. This creates a situation where once a translation is created, the default translation can never be updated with the "Flag other translations as outdated" field checked. Making the entire flagging feature unusuable.