Sharded test builds no longer leak an extra test target per shard

When running tuist test --test-targets with a focused set of tests in sharded CI builds, each shard previously ended up building the alphabetically first test target in the workspace as well. Tuist now prunes and rewrites dangling pre/post-action target references correctly, so only the requested test target is built in each shard.