Changes in collecting plugin dependencies for Jira 8.19 onward upon plugin disabling/uninstalling

Issue Summary

As of Jira 8.19.0 onward when disabling / uninstalling a plugin that is shared and packaged between our apps, another 3rd party app Structure by ALM Works is included in the list of dependent plugins, have to be enabled manually from "Manage Apps" due to errors during re-enabling by Jira.

Steps to Reproduce

1. As of Jira 8.19.0 onward
   disabling/uninstalling Configuration Manager Core Bundle ( installed with Configuration Manager for Jira app v. 6.10.5 and previous versions)
   or
   disabling/uninstalling Configuration Manager for Jira SPI Bundle ( installed with
   Configuration Manager for Jira up to v. 6.10.6)
   results in largely increased number of dependent plugins to be disabled / re-enabled.
2. We observed that for Jira 8.18.0 and lower versions Structure app is NOT included in the list of CMJ SPI Bundle dependent plugins.
   Whilst for Jira 8.19.0 and higher versions, there is about six-fold increase in the number of dependent plugins and
   Structure app is included in dependent plugins list as optional dependency.

It seems that for newer Jira versions (above 8.18.0), changes in the way Jira obtains collection of dependent plugins as well as changes in cutting less significant dependencies, leads to including lots of transient dependencies into collection of dependent plugins.

Structure app relies on some system plugins, and won't start if they are disabled. We observed that after CMJ SPI Bundle is removed, and Jira proceeds with re-enabling of disabled dependent plugins, at the moment Jira attempts to re-enable Structure, several system apps are still disabled. The result is plugin lifecycle error for Structure app due to problem to start its components, thus Structure app cannot be enabled.

Due to integration between Insight - Asset Management app and our app Configuration Manager for Jira, Insight app gets disabled and re-enabled as dependent app when installing/disabling CMJ SPI Bundle (or CMJ Core Bundle) plugin. This potentially may affect core Jira Service Management functionalities as well other 3rd party addons that require on JSM.

Expected Results

When uninstalling / disabling given plugin (root plugin), list of dependent plugins to be disabled/re-enabled is limited to those that require the root plugin

Actual Results

When uninstalling / disabling given plugin (root plugin), list of dependent plugins to be disabled/re-enabled includes also many transient dependencies that do not require the root plugin

Workaround

Dependent plugins, have to be enabled manually from "Manage Apps".