Make RecursionGuard thread-safe,

by maintaining the stack of requests on a per-thread basis.
Made TerminatingWithPathSpecimenBuilder thread-safe,

by maintaining the stack of requests on a per-thread basis.
Added a test to help ensure Fixture remains thread-safe
Improved usage of ConcurrentDictionary by Thread,

because the GetOrAdd method easier to read and more idiomatic. Additionally, using the Thread instance as the dictionary key makes the intended usage more obvious.
Use ForceParallelism and ValueCollectingVisitor in fixture thread test.

Moved SpecimenWithEverything into AutoFixtureUnitTest project, and the IsPopulated() logic was also removed, and is now handled externally (by the test, and the ValueCollectingVisitor).
Use ForceParallelism in concurrent threading tests,

for RecursionGuardTest and TerminatingWithPathSpecimenBuilderTest.
Stop needlessly instatiating a Stack<object> on each GetOrAdd,

in RecursionGuard and TerminatingWithPathSpecimenBuilder.
Incremented patch version,

in order to indicate that making some classes thread-safe is a fix rather
than a new fixture.
Emphasised IEqualityComparer members are a pair

A correct impl of IEqualityComparer needs to implement all members in a
semantically correct manner
Replaced unsafe IEqualityComparer GetHashCode

GetHashCode must not incorrectly bucket objects for a consumer of
IEqualityComparer [`1] to be able to rely on the result of Equals solely
on objects bearing the same hash code being authoritative