Sergei Vorobyov 8c49d77c1a [DependencySubstitution] fix: don't use parent module or library entity source for defining custom entities ...

The module and library entities usually use JPS entity source which can be used for restricted entity set. These entities should be serializable to *.iml files. However, new custom coordinate and substitution entities cannot be serialised into *.iml files. Therefore they should be registered to workspace model with separate entity source.

This entity source replacement can be done for new entities, because it has hard parent reference on the corresponding JPS entities. It means that when parent entity is removed from an entity storage then a custom child entity also will be removed from storage, even if it has the different entity source.

### Issues
  * IDEA-374358 Second scanning degradation on 2025.06.05
  * IDEA-370483 Maven performance degradation related to library dependency substitution


(cherry picked from commit a33a6a93a503abba9a957a4f965f4d305c4d30e3)

IJ-CR-167051

GitOrigin-RevId: f3d833b328709857a8453e3f57d306301e7c9f4b

2025-06-26 22:00:28 +00:00

..

externalSystem/impl

[DependencySubstitution] fix: don't use parent module or library entity source for defining custom entities

2025-06-26 22:00:28 +00:00

java/impl/dependencySubstitution/impl

[DependencySubstitution] fix: don't use parent module or library entity source for defining custom entities

2025-06-26 22:00:28 +00:00

spi/parsing

…