Scope RT0006 error to current compilation only

[olstakh]

This pull request improves the handling of tech debt exceptions in dependency rule analysis, ensuring that exceptions scoped to other projects do not trigger stale exception warnings (RP0006) in the current project's compilation. It also adds new tests to verify this behavior and introduces a build step to clean up stale package artifacts before running integration tests.

Dependency rule evaluation improvements:

• Updated ReportStaleTechDebtProjectExceptions and ReportStaleTechDebtPackageExceptions methods to only evaluate exceptions whose From property matches the current project, preventing false positives for RP0006 when exceptions are scoped to other projects. [1] [2] [3] [4]
• Modified calls to these methods in AnalyzeDependencyRules to pass the current project path as an argument. [1] [2]

Test coverage enhancements:

• Added unit and integration tests (TechDebtException_ForDifferentProject_ShouldNotReportDiagnostic_Async and TechDebtException_ForDifferentProject_NoWarning_Async) to verify that tech debt exceptions for other projects do not trigger RP0006 in the current project. [1] [2]

Build reliability improvements:

• Added a CleanStalePackages target to the integration test project file to remove old .nupkg files from the artifacts directory before resolving project references, preventing tests from running against outdated analyzer code.