fix(model): Skip excluded projects in getDependencies when omitExcluded is true

Previously, getDependencies(omitExcluded=true) only filtered excluded packages
from results but still traversed all projects. This caused inconsistencies when
dependency edges only exist in excluded projects (e.g., test-only submodules).

Now excluded projects are also skipped during traversal, ensuring dependencies
only reachable through excluded projects are not discovered.

Signed-off-by: Kai Hodžić <hodzic.e.k@outlook.com>

Author: voidpetal

model/src/main/kotlin/OrtResult.kt

@@ -243,7 +243,9 @@ data class OrtResult(
         val dependencies = mutableSetOf<Identifier>()
         val matcher = DependencyNavigator.MATCH_ALL.takeUnless { omitExcluded } ?: { !isExcluded(it.id) }
 
-        getProjects().forEach { project ->
+        val projects = if (omitExcluded) getProjects().filter { !isExcluded(it.id) } else getProjects()
+
+        projects.forEach { project ->
             if (project.id == id) {
                 dependencies += dependencyNavigator.projectDependencies(project, maxLevel, matcher)
             }