Introduce StateKind.AttemptingToComplete for partial analysis state tracking

[mavasani]

    >analyzerState?.ResetToReadyState(); [](http://example.com/codeflow?start=20&length=35)

Is the following going to decrease/eliminate the chances of us failing to complete the event because another thread "hijacked" the state after this line?

We could introduce another state, called "AttemptingToComplete". Before executing TryMarkEventComplete, we don't reset the state to "ReadyToProcess", instead we change it to AttemptingToComplete. And only, if TryMarkEventComplete failed, we reset to "ReadyToProcess".

I am not sure if this is going to introduce too much complexity, or, perhaps, a race for completion between different threads.

Originally posted by @AlekseyTs in #65083 (comment)

[mavasani]

This is no longer required as all analysis state tracking code was removed with #66750