Missing config dependencies

Problem/Motivation

I honestly don't know if this is fixable but I'll describe the steps that led to the observation.

When reviewing a merge request adding some schema definitions I noticed the code didn't work. But what was weird was the config ran find, it just didn't do anything. The problem ended up being that the config defined tags that relied on a schema submodule but since the metatag config didn't require the module it wasn't flagged and wasn't caught without manual review since the config validated and imported cleanly.

Steps to reproduce

I guess something like this:

1. Enable schema and a submodule like schema_course.
2. Populate metatag defaults for the course tags.
3. Export the config.
- Observe the lake of dependencies on the metatag export
4. Remove the submodule from core.extension
5. Import the config
- No warnings or failures
- Observe the lack of of schema tags on content despite their definition in config.

Proposed resolution

TBD

Remaining tasks

TBD

User interface changes

API changes

Data model changes