Inconsistent resolution through Virtual repositories via REST API “Trace Artifact Retrieval” endpoint

Problem description: Inconsistent resolution through Virtual repositories via REST API “Trace Artifact Retrieval” endpoint 

Impact:

The inconsistency disrupts scripts/plugins that rely on it to automate processes for all artifacts.

Steps to reproduce:

1. Create a remote Maven repository (ext-maven-maven-central) pointing to Maven Central (https://repo1.maven.org/maven2/) with eager fetching of sources and jars enabled
2. Create a Virtual repository (ext-maven) which aggregates the remote repository created above
3. Perform trace requests to the Virtual repository:
   1. curl https://artifactory.domain.local/artifactory/ext-maven/org/jboss/weld/weld-api-bom/1.0/weld-api-bom-1.0.pom?trace
   2. curl https://artifactory.domain.local/artifactory/ext-maven/com/microsoft/sqlserver/mssql-jdbc/9.4.0.jre8/mssql-jdbc-9.4.0.jre8.pom?trace

Expected behavior:

In the trace output for both requests - “Target repository is not remote or doesn’t store locally” should be equal to “false”

Observed behavior:

In the trace output for 3.1 - “Target repository is not remote or doesn’t store locally” equals “true”