Allow postfix operator called as method after unary postfix hyper operator

currently something like '(my @a = 1)>>.++' fails, since METAOP_HYPER_CALL is called
instead of METAOP_HYPER_POSTFIX. Fixes RT #122342.
Allow dotted form of postfix operator after unary postfix hyper operator, but only for non-wordy operators

The previous version which special cased postfix:<i> only seemed too fragile.
Now the dotted form is allowed only for non-wordy operators.
Remove trailing whitespace
Merge pull request #339 from usev6/nom

Allow postfix operator called as method after unary postfix hyper operator
parse-spec -> helper sub named PARSE-INCLUDE-SPEC
No longre try to do parse-spec tests
Move parse-spec tests to sanity test
Sanity test is not fudged, so fudge manually
RT #123498: Empty binding error in some cases (partial fix)

On MoarVM, if unexpected named parameters came in through capture or hash
interpolation, the error message would be empty.

An "if $error" would be false in the case, because $error is usually an empty
array. Changing it to an "if nqp::defined($error)" as the rest of the code
uses should prevent error messages from going missing.
native-type some constants in the binder

should not make things slower, I hope :-)
Micro-optimize Routine.assuming
signatures are also allowed to have invocants :)
allow @a[0,2...*] to work again
Merge branch 'nom' into newio