Content translation entity bundle specific settings now use third party settings on language configuration

The global functions content_translation_set_config(), content_translation_get_config(), content_translation_get_config_key() and content_translation_enabled() are now moved to the content translation manager service as setEnabled() and isEnabled(). The storage is now based on language.settings configuration replaced by configuration entities per bundle.

Before in Drupal 8:

content_translation_set_config('comment', 'comment_article', 'enabled', TRUE);
content_translation_enabled($entity_type_id)

Now in Drupal 8:

$content_translation_manager = \Drupal::service('content_translation.manager');
$content_translation_manager->setEnabled('comment', 'comment_article', TRUE);
$content_translation_manager->isEnabled($entity_type_id)
$content_translation_manager->isEnabled($entity_type_id, $bundle)

Instead of one global content_translation.settings file the settings are distributed in language.content_settings.$entity_type.$bundle.yml files under third party settings.

Before:

content_translation.settings.yml

comment:
  comment:
    content_translation:
      enabled: 0
node:
  article:
    content_translation:
      enabled: true
  page:
    content_translation:
      enabled: 0

After:

language.content_settings.node.article.yml

uuid: 13375bbd-0afe-467d-a404-4e264997d3ca
langcode: en
status: true
dependencies:
  config:
    - node.type.article
id: node.article
target_entity_type_id: node
target_bundle: article
default_langcode: current_interface
language_alterable: true
third_party_settings:
  content_translation:
    enabled: true