Provide a follow-up task to uninstall a module

Problem/Motivation

Now that ModuleActivator can expose tasks, a logical one we might want to include is a task to uninstall the module. The main benefit I can see is that people who installed a module via PB can go to PB to uninstall it, rather than having to figure out a whole other form. That seems like a very sensible idea for UX.

Proposed resolution

We'll need to create a route, something like /admin/modules/browse/uninstall?module=foo which programmatically submits \Drupal\system\Form\ModulesUninstallForm, redirects to the confirmation form, then redirects back into Project Browser after the user has confirmed the uninstall.