Remap plugin problems when resolving plugin dependencies

[novotnyr]

Plugin dependencies that are resolved as standard Platform plugins might contain problems.

Some plugins, including those from JetBrains, may have problems leading to error-level plugin problems. In such cases, these plugins are not resolved as dependencies, which can result in unexpected reports of missing dependencies, even when they are actually available.

• Introduce a new PluginInfo type: DependencyPluginInfo that wraps any other plugin info. This indicates a plugin that will be resolved as a dependency.
• Introduce a repository that delegates to other repositories and treats the results as DependencyPluginInfo instances.
• Make corresponding PluginInfo instances aware of the IdePlugin via explicit interface when appropriate
• AbstractPluginDetailsProvider allows to customize the creation of the plugin on the subclass-level.
• DefaultPluginDetailsProvider and SizeLimitedPluginDetailsCache are dependency-aware. They are using different strategy when resolving plugin as a dependency. More relaxed plugin problem rules are put in place.