Issue Summary

When accessing the Dependency Grid for a Program, dependencies linked to Features are displayed in the grid with a Program label in the Type column (because both teams involved are Program teams). However, when the Type = Program Dependency filter is applied, these same dependencies are excluded, only dependencies linked to Epics/Capabilities are returned.

Steps to Reproduce

1. Navigate to a Program > More Items > Dependencies
2. Create 2 dependencies, both with Programs as the Requesting/Depends On target:
   1. Dependency A → linked to a Feature
   2. Dependency B → linked to an Epic
3. Observe the Dependency Grid, both display as "Program Dependency" in the Type column
4. Apply the filter Type = Program Dependency
5. Observe:
   1. only Dependency B (Epic-linked) is returned
   2. Dependency A is excluded despite being shown as Program-level in the grid

Expected Results

The Type filter should apply the same derived-type logic used by the Dependency Grid, treating a dependency as Program-level when the involved teams are Program teams.

Actual Results

The Type filter strictly evaluates tblDependency.TypeID = 6, excluding Feature-linked dependencies

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available