Add plugin class module dependencies to dependency calculation

Problem/Motivation

In 📌 Move multiple provider plugin work from migrate into core's plugin system Active , plugin class dependencies (such as the plugin class extending a class, implementing an interface, or using a trait from a different module) were found via Reflection and added as a property on the plugin definition. These dependencies include the provider (module, in other words) list of the class/interface/trait.

Though these module dependencies exist in the plugin definition, they may also need to be included in the dependency calculation for configuration that uses these plugins, so that module uninstallation can be acted on appropriately.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet