[D8] HTML importer

Hi! Thanks for your contribution. Right off the bat, the project name is html_importer but your code uses html_import. It would be easier for users downloading and using your site to stay consistent with the naming.

Also there are several things to check on your PAReview and to fix. https://pareview.sh/pareview/https-git.drupal.org-project-html_importer

Added pareview link to main issue body

8.x and dev are wrong names for branches. A correct one would be 8.x-1.x, for example. A new branch needs to be created, made the default one, and the other branches need to be removed.

We are just waiting for reviews.

Thanks for your contribution!

Review of the 8.x-1.x branch:

1. Sounds like your module depends on the node module, but that is not listed in html_importer.info.yml?
2. user.role.creator.yml: Drupal sites probably want to define their own roles and don't want a contributed module to ship a "creator" role. That could easily clash with an existing creator role on their site, so probably best if you remove the role.
3. ImportHtmlForm: why is this class a ConfigFormBase? You are no saving any configuration entity here? I think it should just extend from FormBase?
4. file_default_scheme() and file_prepare_directory() are deprecated. Please check your code for deprecated functions and use the suggested replacemnts instead.
5. bathProcess(): typo, should this be called batchProcess() instead?
6. bathProcess(): why do you catch Throwable and then just re-throw it as exception? Please add a code comment or remove it.
7. nodeDashboard(): you are performing one query for each file iteration, which can be expensive when there are many files. Could be optimized to load all file IDs at once I think.

Did not see any security issue otherwise, looks good to me!

Thank you for your contribution! I am going to update your account.

These are some recommended readings to help with excellent maintainership:

• Dries' post on Responsible maintainers
• Best practices for creating and maintaining projects
• Maintaining a drupal.org project with Git
• Commit messages - providing history and credit
• Release naming conventions.
• Helping maintainers in the issue queues

You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

I thank all the dedicated reviewers as well.