Fixes UNT0022, when reusing transform

[sailro]

Fixes #428

Checklist

• I have read the Contribution Guide ;
• There is an approved issue describing the change when contributing a new analyzer or suppressor ;
• I have added tests that prove my fix is effective or that my feature works ;
• I have added necessary documentation (if appropriate) ;

[Copilot]

Pull request overview

This pull request fixes issue #428 in the UNT0022 analyzer, which incorrectly suggested combining separate transform.position and transform.rotation assignments into a single SetPositionAndRotation call when doing so would change the code's semantics. The fix adds detection for cases where the first property being set is referenced in the calculation of the second property.

Key changes:

• Added DetectExpressionReuse method to check if the first statement's property is referenced in the second statement
• Integrated the reuse detection into the analysis flow to prevent incorrect optimization suggestions
• Added comprehensive test coverage for both unsafe (direct reuse) and safe (variable-based) scenarios

Reviewed changes

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

File	Description
src/Microsoft.Unity.Analyzers/BasePositionAndRotation.cs	Added expression reuse detection to prevent semantically incorrect optimizations
src/Microsoft.Unity.Analyzers.Tests/SetPositionAndRotationTests.cs	Added tests for expression reuse scenarios, including both cases that should and shouldn't be optimized

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

@sailro I've opened a new pull request, #430, to work on those changes. Once the pull request is ready, I'll request review from you.