Dependency agent starts with a wrong dependency for fqdn search that leads to either issue not being resolved or excessive dependency tasks

[pranavgaikwad]

Sometimes the dependency agent cannot come up with a correct fqdn to search for. See this example, when analysis agent adds an import:

import io.smallrye.reactive.messaging.annotations.Blocking

The dependency agent sometimes makes the search for artifact ID that does not exist. Then we can't do much after this point as the agent started off with the wrong artifact. This leads to issue not being fixed at all and/or multiple calls.

In order to truly solve this, we have to augment that initial suggestion by the model for a given group and artifact. AFAIK we can do this several ways - making a search on javadoc and/or maven for full import hoping that we will find several matches, doing a generic google search, augment the rule to hint possible options to choose from for a given target technology.