New administrative page to opt-in configuration entities for views support

While I believe I may have found a fix to the excessive memory usage, I still think adding this administrative page would allow admins to choose to override the default behavior of the module and limit the configuration entities used by the system.

The module can then use this page as a kind of feature flag page to provide sensible defaults that allows the module to work even if a module has crazy complex config that blows it up. The admin will have to choose to enable that and see how it blows up (in a hopefully safe, local environment) first.

Sort of like how you did it in Config View module here?