Move default views into their respective module config directories

It seems to make sense to do this step by step in every actual conversion issue (tracker/frontpage etc.) and just keep the other ones here, maybe?

+++ b/core/modules/views/lib/Drupal/views/ViewStorageController.phpundefined
@@ -16,21 +16,6 @@
-   * Overrides Drupal\config\ConfigStorageController::load();
-   */
-  public function load(array $ids = NULL) {
-    $entities = parent::load($ids);
-
-    // Only return views for enabled modules.
-    return array_filter($entities, function ($entity) {
-      if (module_exists($entity->get('module'))) {
-        return TRUE;
-      }
-      return FALSE;
-    });
-  }

I'm wondering what happens if we had node installed, then views got enabled and then node get's removed again. The config files might not dissapear and then you end up with loading unwanted files?

Maybe we should ask heyrocker about that, but that's maybe/probably done by the config system itself?

I propose to move the actual used views, but keep the example views (like glossary) in views.

Fill that as a novice task.

I've started to look at this task because of the 'Novice' tag. I think due to the age of the issue many things have changed, or even got resolved.
comments_recent was moved to comment module, archive+frontpage+glossary were moved to the node module, taxonomy_term to the taxonomy module. I couldn't find the tracker and backlinks views, they were possibly renamed.
The controller, which is modified in the patch [ViewStorageController] I think was also removed/implemented elsewhere/in different way.