Ensure the new DS analyzer handles its execution when no compatible files are found

Why are we doing this work

To support existing projects which may not have a supported file commited to the repository, we will trigger the DS job based on additional files (e.g. pom.xml).

This means the analyzer could be executed in a context where no compatible file is actually present. We must ensure the behavior is providing a good UX and possibly assist the user in setting up their project accordingly.

See #501103 (comment 2245718439)

Relevant links

Non-functional requirements

• Documentation:
• Feature flag:
• Performance:
• Testing:

Implementation plan

• add a warning message to improve UX when we cannot identify a lock file.
• verify the behavior of the analyzer when running in this situation
• if needed, adjust the analyzer behavior (exist code, logging)
• Exit with a non zero code in case a warning was printed