I add this rule because when you create a new class and define a trait
before creating a constructor (for example).
When you create the constructor and you complete the attribute from it
(transformation action) then the properties were added before the trait
which was always a pain to correct manually.

Append a blank line before the propertiess to add if they are added
after something else than the class's opening brace or another property.

Before we made a decision that if a property has a type it will have a
phpdoc block because it was the only way to declare the type.

I don't like this because this logic depends on the templates and don't
have its place here anymore.
So I removed it and added the blank line directly in the template if
there is a phpdoc block.

Plus it fix the issue when inserting multiple properties for the first
time (no property in the class yet), then even if the properties have a
type there were no blank line between the properties.

Note: There is two cases where the blank line is a problem, when:
- the property is inserted after the class's open brace
- the is inserted after something else than the class's open brace or
another property

Append a blank line but only when the first thing in the class is a
method declaration.
Otherwise there is already a blank line before the method declaration.

It makes more sense and goes along with `nextMember` that was already
used.
We were already checking that `lastProperty` was an instance of
`PropertyDeclaration` which proove that the name was not suited.

Reduce a bit the code and simply the loop.
`reset()` return `false` if the array is empty, that's why I default it
to `null`.

Moving the blank line before a property in the template have created a
few issue, as mentionied in the commit in question.

This commit updates the unit tests to take those "side effects" into
account.