TUnitExtensions:GetConstructorParameterNames throws "Could not find constructor with 0 parameters" when using a Test Class with a TUnit [ClassConstructor]

[Simonl9l]

First glance at this verification package is very intriguing! I like the concept of Snapshot testing, an am keen to get running.

It seems Verify is trying to find a Test Harness Class constructor with zero parameters.

Could not find constructor with 0 parameters.
   at TUnitExtensions.GetConstructorParameterNames(Type type, Int32 argumentsLength) in /_/src/Verify.TUnit/TUnitExtensions.cs:line 49
   at TUnitExtensions.GetParameterNames(TestDetails details) in /_/src/Verify.TUnit/TUnitExtensions.cs:line 7
   at VerifyTUnit.Verifier.BuildVerifier(String sourceFile, VerifySettings settings, Boolean useUniqueDirectory) in /_/src/Verify.TUnit/Verifier.cs:line 47
   at VerifyTUnit.Verifier.<>c__DisplayClass8_0.<<Verify>b__0>d.MoveNext() in /_/src/Verify.TUnit/Verifier.cs:line 67

TUnit allows the use of a Class Constructor Helpers that I am using to inject services in the the constructor as parameters, and my tests won't work with out them - integration testing!

I'm not sure why Verify is trying to find such a construct on the Test Harness Class, than the objects being verified - and not finding anything in the docs, issues or discussions, that can help me.

Is Verify compatible with all TUnits features?

[SimonCropp]

fix incoming #1362