Validate that extension listed in the config.import section of recipe.yml has option to bypass all config of that extension

Problem/Motivation

This is spun off from #3400672: Robustly validate the structure of recipe.yml.
In https://git.drupalcode.org/project/distributions_recipes/-/merge_request..., Alex wrote

Hmmmm... this is super super tricky. I'm not sure that tour: ~ means quite what you think it does. If tour provided simple config for example a tour.settings config then this would be created.

Which means that even if we say tour: ~ or dblog: ~, to not import any of the config, dblog.settings will be get imported.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes