Remove some types of false positives from Eraser's data race reports

[acizmarik]

This PR does the following changes:

• Fix shadow variable state transitioning (previously we mistakenly marked some situations as racy)
• Fix field access ordering events around .cctor
• Track last write access for every shadow variable (previously we could have dropped state that was necessary for reports)
• Add suppression SuppressAnalysisOfStaticDelegates that skips analyzing static fields with type Delegate as it generates a lot of noise. Roslyn uses this a lot following pattern to compile, for example lambdas:

	.class nested private auto ansi sealed serializable beforefieldinit '<>c'<T>
		extends System.Object
	{
		.custom instance void System.Runtime.CompilerServices.CompilerGeneratedAttribute::.ctor() = (
			01 00 00 00
		)
		// Fields
		.field public static initonly class System.Buffers.SharedArrayPool`1/'<>c'<!T> '<>9'
		.field public static class System.Func`2<object, bool> '<>9__11_0'
	} // end of class <>c

• There is a public mutable field <>c.<>9__11_0 whose initialization is not synchronized. There can be multiple places that use the field. Its initialization is racy but since delegates are immutable and always point exactly to the same place, it is benign