Resolving Managed Version Source doesn't work for indirect version definitions

[pbodnar]

I think this worked before, it is reproducible e.g. on Eclipse 2023-06.

Now that eclipse/lemminx-maven/pull/298 got implemented, artifact's managed version and its source is shown once again. But it doesn't seem to display the correct source of the managed version definition when the version is defined indirectly. This is reproducible e.g. with https://github.com/apache/logging-log4j2/:

• root parent pom.xml defines:

       <dependency>
          <groupId>org.junit</groupId>
          <artifactId>junit-bom</artifactId>
          <version>${junit-jupiter.version}</version>
          <type>pom</type>
          <scope>import</scope>
        </dependency>
  

• log4j-api-java9\pom.xml references the parent pom and a dependency:

        <dependency>
          <groupId>org.junit.jupiter</groupId>
          <artifactId>junit-jupiter-engine</artifactId>
          <scope>test</scope>
        </dependency>
  

• INCORRECT source is linked in the hover: The managed version is 5.9.2. The artifact is managed in [org.junit.jupiter:junit-jupiter-engine:5.9.2](file:///C:/...)