Fix state matching logic in AndroidSyncFrameworkTest

[rfc2822]

Purpose

Currently test runs are randomly failing because AndroidSyncFrameworkTest doesn't correctly take optional sync states into account.

Short description

This PR optimizes handling of partial state comparision and adds a "full match required" flag that disables partial state comparision.

Checklist

• The PR has a proper title, description and label.
• I have self-reviewed the PR.
• I have added documentation to complex functions and functions that can be used by other modules.
• I have added reasonable tests or consciously decided to not add tests.

[Copilot]

Pull Request Overview

This PR fixes test flakiness in AndroidSyncFrameworkTest by improving the state matching logic to properly handle optional sync states during partial and full comparisons.

• Refactored state assertion logic by separating comparison from error handling
• Added a fullMatch parameter to control whether all expected states must be matched
• Added validation to ensure the last expected state is non-optional

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sunkup]

Context is not used, so we don't need to inject it. Furthermore no mocks are used so we don't need the mock rule. Looks good to me otherwise though.