Evaluate methods with short array syntax type hints correctly

[jwoschitz]

If methods had a type hint like "MyClass[]" then the expected result was an instance of "MyClass[]". Instead it should be an array of "MyClass".

This PR contains the following change:
if a type is suffixed with "[]" the type gets replaced by "array" during the parsing phase.

See tests for further details.

[rtens]

I totally agree with your observation but I don't think the scenarios you added describe the behaviour very well. IMHO, if a value matches a type, the fact that the type is returned is not as important as the fact that no exception has been thrown because it contrasts with the non-matching case.

So I added these two scenarios instead, one checking that the value is correctly inferred from the hint, the other checking that the type checking works correctly.

At that point I noticed that the type checking scenarios should have their own specification and also all follow the pattern of asserting exceptions vs. non-exceptions. So I restructured them.

I hope these changes are in your favour.