bug: TimeoutCancellationTokenAnalyzer only validates last parameter

[thomhurst]

Description

File: TUnit.Analyzers/TimeoutCancellationTokenAnalyzer.cs (Lines 43-63)

The analyzer only checks if the last parameter is a CancellationToken. It doesn't validate:

1. That CancellationToken is the only parameter after the context parameter
2. That if there's a TestContext parameter, CancellationToken comes after it
3. Methods with multiple parameters where CancellationToken isn't last

Impact

False negatives — methods with wrong parameter order (e.g., Method(CancellationToken ct, TestContext ctx)) won't be detected.

Suggested Fix

Validate parameter order more thoroughly:

Valid:   (TimeoutContext ctx, CancellationToken ct)
Valid:   (CancellationToken ct)
Invalid: (TestContext ctx) - missing CancellationToken
Invalid: (CancellationToken ct, TestContext ctx) - wrong order