Parameter default value builds wrong parse tree

[ghost]

The default value in this example is treated as part of the "as type clause", which is wrong and probably because of the expression rule in complexType. One way to solve this could be to introduce a new typeExpression and copy over only the expression parts (e.g. without EQ) that are allowed in type expressions. That could also simplify the new / typeofis expression rules. We would have to deal with duplicate expression context classes though.

Public Sub Test(ByVal a As Integer, Optional foo As Object = Nothing)
End Sub

Edit: The create-declaration method in the declarationssymbollistener + the type annotation pass would have to be changed at least.