Shell blueprint is missing dependencies

[gvkries]

Describe the bug

During startup, the ShellContainerFactory is relying on the ShellBlueprint.Dependencies property to get all startup classes that needs to be added to DI. But if an extension contains only features that do not match the extension ID, dependencies without any feature assignment are not added to the blueprint at all.

That means that some startup classes not executed at all.

Orchard Core version

Reproducible in 1.8.3 and later. I didn't check earlier versions.

To Reproduce

1. Enable the features Microsoft Entra ID Authentication and Deployment.
2. Create a deployment plan and add steps to it. The Microsoft Entra ID step is missing there, because its startup class OrchardCore.Microsoft.Authentication.DeploymentStartup is not executed.

Expected behavior

All startup classes which meet their dependencies should be executed.

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[Piedone]

Did you notice any other features affected in the current source?

[gvkries]

This is a general issue, but I didn't search for other cases explicitly.