Improve field access in complex multilingual and content moderation scenarios

Problem/Motivation

I believe IEF can be improved in terms of visibility of fields in scenario that involve translation forms with content moderation.

Steps to reproduce

Attached is a patch that reproduces the following scenario:

- node type ief_node_type_host
  - is translatable
  - has 2 entity reference fields (both with widget IEF simple):
    - ref_to_node_type_1:
      translatable
      references nodes of bundle ief_node_type_nested_1
    - ref_to_node_type_2:
      untranslatable
      references nodes of bundle ief_node_type_nested_2

- node type ief_node_type_nested_1
  - is translatable
  - is set to have untranslatable_fields_hide: '0'
  - has fields:
    - field_translatable_textfield (translatable)
    - field_untranslatable_textfield (untranslatable)

- node type ief_node_type_nested_2
  - is translatable
  - is set to have untranslatable_fields_hide: '1'
  - has fields:
    - field_translatable_textfield (translatable)
    - field_untranslatable_textfield (untranslatable)

When you go to a translation form on the host node:

• for the first reference field (ref_to_node_type_1):
• you should see both the translatable and untranslatable text fields,
  because "Hide non translatable fields on translation forms" is NOT
  checked for the referenced entity type (ief_node_type_nested_1).
• you should see for the untranslatable field the "(all languages)" clue.
• for the second reference field (ref_to_node_type_2):
• you should see only the translatable text field, because "Hide non
  translatable fields on translation forms" is) checked for the referenced
  entity type (ief_node_type_nested_2).