Fixes handling of methods Task.WaitAsync and SemaphoreSlim.WaitAsync

[michelebastione]

Description

This PR addresses two closely related bugs that caused entire method bodies being inadvertently dropped at the invocation of Task.WaitAsync or SemaphoreSlim.WaitAsync.

Both issues originated from a syntax check for the string "WaitAsync":

1. In AsyncToSyncRewriter.ReplaceAsync the pattern matching for case MemberAccessExpressionSyntax lacked a fallback for validation purposes (when called from EndWithAsync). Hence WaitAsync calls chained at the end of a method (e.g., FooAsync().WaitAsync()) made the entire expression chain always return null, leading to them ultimately being discarded.
2. Due to the check being based solely on the ExpressionSyntax value, there was no differentiation between Task methods, which are supposed to be dropped, and methods such as SemaphoreSlim.WaitAsync, which should be converted to SemaphoreSlim.Wait instead. As a result, synchronization primitives were being deleted from the generated code.

Changes Introduced

1. More clearly separated the concerns of methods ReplaceAsync and EndsWithAsync. The latter now implements a fallback to a non null value for the MemberAccessExpressionSyntax pattern matching case, thus preventing the entire chain call to be dropped.
2. Added the TryReplaceIdentifier method that uses the code block's SemanticModel for making sure that a symbol called "WaitAsync" is removed only when its containing type corresponds to System.Threading.Tasks.Task or System.Threading.Tasks.TimeProviderTaskExtensions.

fixes #119
fixes #121

[michelebastione]

I assume the failed job is simply due to the fact that there is no package ready to be published, as I noticed the same error in other PRs, but do let me know if there's anything I'm supposed to fix.

[virzak]

Hi again, @michelebastione,

Thanks for the contribution.
I removed some of the boilerplate code from the test cases and fixed the GitHub actions.

[virzak]

Your changes are in 2.0.15 on nuget

[michelebastione]

Thanks @virzak! We've been hard at work on MiniExcel, in the past year we fixed 100+ issues and added many new features, and your project definitely helped us navigate through it more swiftly. Now that we're almost ready to release the full fledged v2 I thought it could be a good moment to take a step back and give back a little, so here I am lol.
If you're still using MiniExcel please feel free to leave us more feedback on what you would like to see fixed or implemented before we ship the new version!