…ndencyReference(to:from:)

This allows a unified path for applying platform filters

This covers two scenarios

Apply platform filters to transitive dependencies if they exist in intermediate steps
Given: A -> (.ios) B and B -> C
Then: A -> (.ios) C

Remove dependencies if intermediate filters result in a disjoint set
Given: A -> (.ios) B and B -> (.macos) C
Then: A -> C should have `nil` platform filters, which results it it being removed as a transitive dependency.

These remove the “already visited” and “leaf dependency” branches from our traversal.  Including `[]` causes our logic to incorrectly resolve to filters when these branches should be excluded from that calculation.

This changes things so that `[]` no longer represents a filter that applies to all.  We will convert from `.all` to `[]` when we apply so that the Xcodeproj value is accurate, but within Tuist logic we need to distinguish between being applied to all platforms and none and unset.

…pping

Only call `platformFilters(from:to:)` within this method to reduce chance of divergent logic.

This covers two scenarios

Apply platform filters to transitive dependencies if they exist in intermediate steps
Given: A -> (.ios) B and B -> C
Then: A -> (.ios) C

Remove dependencies if intermediate filters result in a disjoint set
Given: A -> (.ios) B and B -> (.macos) C
Then: A -> C should have `nil` platform filters, which results it it being removed as a transitive dependency.

…m:)` to resolve filters

…ests`

This will filter out windows, linux, and other platforms when a dependency is exclusively conditional on them.