Implement Supply.categorize
Make sure we test Supply.categorize
Announce Supply.(classify|categorize)
Emphasize specialness of "$( )" vs "$()"
Fix typo spotted by vendethiel++
remove bogus literal complex rule

We should not have a special literal rule for 42i, for several reasons:
First, it's incorrect in the face of language extensibility, since
someone could add a different affix that overrides i in either
precedence or semantics.  Second, the rule was incorrect anyway, since
it didn't check for a word boundary after the i.  Third, we can and
should rely on constant folding these days to reduce 42i to a literal
value when it's appropriate (and refrain from doing so when it's not).
Fourth, a literal complex ought to be written with angles anyway,
if you don't want the constant folder to get involved.  That's why
that construct is there.  Fifth, this fixes the double warning on
(non)-octals beginning with 0, since the complex rule was calling the
integer rule and then backtracking in the absence of an i.
Temporary fix to get List.permutations to work
Temporary fix for #121830
Pair.key is *not* rw, as per S02:1704
Add some comments, make error message show value
Mention ro-ness of Pair.key
Make signal() a bit more picky on what to accept

At compile time, if only 1 signal
Make sure we send Signal to executed code

Rather than just the int that we got from the OS
Make sure we do each given signal once
Move tests outside of loops for better performance
Optimize out %_ when unused.
Avoid unrequired container allocs in p6decontrv.
Get latest NQP/MoarVM, with various optimizations.
Supply.grep now allows simple smartmatch semantics
Make sure we do all Promise tests