Allow bracketed expressions in ZenType declarations.

[eutro]

This can reduce ambiguity and possibly allow for function arrays, or associatives with function values, if ZenTypeFunctionCallable#toJavaClass ever gets implemented.

[kindlich]

Hm... not sure if I like that you made every array and map type be printed in brackets 🤔

Because people will be confused if it suddenly writes expected (IIngredient)[] what the () are for

[eutro]

Without the parentheses, stringifying (function()int)[] would become function()int[], though, which is not the same.

Brackets are a common thing to group expressions, so I don't think people will be too confused, though I'll admit it might look ugly.

[eutro]

It might make sense to have ZenTypeFunction stringify including the parentheses instead, since it's the only type where it makes a difference.

[kindlich]

Hm... I still wonder if we should add these () all the time, or only when needed?

Like, afaik, we only need them for the combination of arrays and functions.

So, thinking:

• We could have the array's name to only add the () if it's a function
• We could give ZenType a new method that determines if it needs them.

Sure, an extra set of brackets should not irritate experienced developers.
However, printing the type in another form than that which the user inserted can be irritating to especially new developers.