Start using setmultispec on MoarVM.
Auto-gen'd protos don't need special vars.

We will never look at them or use them, so don't waste time/space on
having them.
Partial fix to regressions from setmultispec work.

We need to make onlystar protos consistently not show up in caller
introspection to make this reliable. We need that for not getting
CALLER:: wrong in thunks anyway, so might as well implement it.
Mark onlystar protos as thunks.
Assorted updates now that onlystars are thunks.

This fixes many long-standing inconsistencies when we skip over any
onlystar protos. The multispec optimization forced the issue, but it
has existed for a couple of years, since we started inlining or doing
multi-sub compile time call optimization. Note, updates will be needed
for the JVM and Parrot backends to cope with these changes.
A cheat for Parrot to fix failing tests.

This along with the NQP patch gets this branch fuctioning well on
Parrot; the multispec itself isn't used, but the improvements to proto
and CALLER::/OUTER:: pseudo-package interaction now work out on Parrot,
and future fixes to OUTER:: with regard to thunks should work too.
Unbust build on JVM.
Don't try running Parrot test on JVM.

It skips rather than blows up, but it's still pointless to try.
Bump to NQP with multispec/thunk support.

multispec only takes effect on Moar, but all backends get the proto
onlystar CALLER:: improvements and infrastructure for fixing other
thunky things.