Fix incorrectly handled paths for file include reason

[sheetalkamat]

We didnt consider the ".ts" to "d.ts" redirection when setting file include reason which resulted in missing changes when included file was from referenced project from two different imports. We would pick whichever was used first and miss other
Also added extra test validation on each program to verify this for future refactors and tests

Thanks @gabritto from sharing this in #1714 (comment)

[Copilot]

Pull Request Overview

This PR fixes a bug where file include reasons were not properly tracked when files were redirected from .ts to .d.ts, causing missing import information in TypeScript build outputs. The fix ensures that include reasons are correctly propagated through file redirections, particularly for referenced projects with multiple import paths.

• Fixed incorrect file include reason handling for .ts to .d.ts redirections
• Added validation to verify include reasons are properly set for all program files
• Updated test baselines to reflect corrected import tracking behavior

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
internal/compiler/filesparser.go	Modified include reason logic to handle redirected files and added helper function for proper reason propagation
internal/compiler/fileloader.go	Added missing files to processed files structure
internal/compiler/program.go	Added testing methods to expose include reasons and missing file checking
internal/execute/tsctests/sys.go	Added validation logic to check include reason consistency and baseline reporting
internal/execute/tsctests/runner.go	Updated baseline generation to include include reason validation results
Test baseline files	Updated baselines showing corrected "Imported via" information in build outputs