Recommendations are null for a long time after generation of stack report

[rootAvish]

Issue Overview

In some cases instead of the Maven insights model Kronos is getting the recommender call.

Expected Behaviour

The call should go to the Maven model when no vertx, spring, wildfly components are present.

Current Behaviour

Companions are taking a long time to show up, due to Kronos being used as the recommendation service.

Steps To Reproduce

1. Run stack analysis on the manifest file: https://github.com/apache/maven/blob/master/maven-core/pom.xml, companions will not show up for a long time

[miteshvp]

@rootAvish @sara-02 @abs51295 - increasingly it might get difficult to debug where the request is served from if we have more models serving an ecosystem. Ideally we should send an additional information in the response such as model_scored : KRONOS / HPF / etc. for each recommender request. WDYT?

[rootAvish]

@miteshvp Agree, should be easy to add and would be a nice QOL improvement.