Identify roadmap to release 2.0.0

Problem/Motivation

There's no clear path to release.

Many organizations are restricted from adopting contributed packages and modules that are not a stable release or under security review.

Proposed resolution

Help the community know which tickets to prioritize.

It would be great if there was a roadmap to identify which existing or new issues need to be completed in order to get over the release hurdle.

Remaining tasks

• [ ] Attempt to replicate existing bug issues and close any that cannot be replicated.
• [ ] Prioritize (low or high) issues and feature requests based on their pertinence to release 2.0.0.
• [ ] Mark items necessary for release as "Release blocking" and "release 2.0.0"

Worth mentioning issues

• Do not reimport existing entities 🐛 Do not reimport existing entities Needs review
• Add example module, or document how to make default_content_test installable 📌 Add example module, or document how to make default_content_test installable Fixed
• Drush command to delete default content →
• Handle exceptions during import 🐛 Handle exceptions during import Needs review
• Allow manual imports ✨ Allow manual imports Postponed