Move statistics_node_translation_counter to Statistics module

Ready for review

Change makes sense and needed to deprecate statistics probably.

Committed/pushed to 11.x and cherry-picked to 10.3.x, thanks!

I realized this morning that moving a multi-lingual migration out of content_translation might cause problems because they were placed in content_translation so they were not discovered.

I did some local testing and confirmed that the statistics_node_translation_counter is now discovered when content_language is not installed. Ideally, that should not happen but it is working as designed.

This means that this translation related migration will always run when using the 'one click' upgrade or similar drush command. Fortunately, that does not cause errors because this migration is to support the Classic node migrations. The 'one click' upgrade uses the Node Complete migrations where d6_node_translation and d7_node_translation are not used. When statistics_node_translation_counter runs every row will be skipped because migration_lookup will return a NULL.

  nid:
    -
      plugin: migration_lookup
      migration:
        - d6_node_translation
        - d7_node_translation
      source: nid
    -
      plugin: skip_on_empty
      method: row
    -
      plugin: extract
      index:
        - 0

quietone → closed merge request !6785

Automatically closed - issue fixed for 2 weeks with no activity.