Exclude rather than include configuration

Problem/Motivation

First, you can use a * wildcard to install all configuration the module provides, just as would happen when the extension is installed "normally" (not via a recipe). In most cases, this is the recommended approach.

Thinking of what we've done with profiles in the past this would be the case too, there would be specific configuration that wants to be excluded, and probably an alternative supplied, but all other configuration included by default.

Proposed resolution

As such it would seem desirable to default to include all module configuration, and to have options to exclude specific configuration, or all configuration.

Remaining tasks

User interface changes

API changes

Data model changes