Rename the module to match its potential [#3624233]

Problem/Motivation

Looking at the module name, it sounds really confusing and very much below the potential this module has.

I think historically it might have started from syncing / importing single entities, but has become a widely used, very helpful module for exporting / importing / syncing content entities across (same, similar or even different) Drupal installations.

When goding the next step making this a swiss army knife of content entity syncing and importing through #3624228: Add a review (& mapping) step on import I think it would be worth discussing a rename for the next version.
Or are there better alternatives already solving the same?

I think better names might be like:

Content Entities Sync
Content Entities Import, Export and Sync
Content Entities Migrate
...?

Currently there's a mental mismatch between the power of the module and "Single"?

Technically this would of course mean to create a new Drupal module project, move the module over and deprecate the old one, but in my eyes it's worth it for clarity and future development.