When a module providing a base table is uninstalled, delete all views built on it

1. +++ b/core/modules/views/views.install
   @@ -27,3 +27,29 @@ function views_schema_0() {
   +  if ($tables) {
   

   I think we should add !empty check here.

2. +++ b/core/modules/views/views.install
   @@ -27,3 +27,29 @@ function views_schema_0() {
   +    $views = $view_storage->loadMultiple($query);
   

   Do we have to check $query is empty or not?

+1 in general.

Field module prevents module uninstall if a field providing module has an active field/instance, this is nuking views if the module is uninstalled. I think we need to pick one set of behaviour for config that's dependent on multiple modules and stick with it, so postponing on #2080823: Create API to discover config entities' soft dependencies and use this to present a confirm form on module uninstall.

Actually postponing...

I tested this last night and the interesting thing is that whilst the frontpage view remains in active config after uninstalling node the view is not listed in views ui and the path returns a 404. So I'm not 100% certain we have a bug.

The problem would be when node module is eventually re-installed one day. If node changes its views plugins in the meanwhile, it'll have updates that update existing views to fix them (or there'll need to be some other mechanism to update the config to match new plugin IDs). However since node module is uninstalled, those updates won't run - then when node module is re-enabled what's the status of the view that's in active config?

This will be handled by the config dependency system - #2267453: Views plugins do not store additional dependencies