Readme update, additional tests, test reordering

Less than surprising release, an addition to the README following some of the changes made today and a revelation or two.

Version match to NPM

Stability double-checked on windows machines, primary same as v1.0.2

Oops! Slippage in recursion and releases

A fix to prevent slippage in the recursion-tracker made a couple of months back was not rolled into a release, and thus not pushed out to NPM. Mostly my bad for taking so long to notice the NPM repo and github repo were not tracking togeather.

Updated readme, naming, exports, and fixes to antipattern behavior

• Plugin name finally reflects... the actual name of the plugin
• Exported function (though unlikely to have been ever used in anyone's config as there is no config) is now appropriately named, and hypothetically could break some oddball configurations, but as this is an extreme edge-case, the version bump will remain minor
• Fix to antipattern detection, will now correctly interpret positions when extensions are outbound from media queries, or default to not warning (when it can't detect positions)
• Readme updated for consistency, and grammatical correctness by everyone's favorite @kswedberg

Update to use PostCSS 5 (no usage shift)

Update courtesy of @jonathantneal, to update syntax to support PostCSS 5, will not shift or break from any previous use case.

The large version shift is only due to the nature of PostCSS 5's lack of support by other postcss plugins.

Antipattern CSS detection and warning, and media-cross-media warning

Added warnings (and tests for those respective warnings) for the use of @extend in an anti-pattern, as well as attempts to extend a media query from inside a media query (directly disallowed)

Infinite recursion detection improvements, widespread minor corrections

User-made infinite loops of @extend should be fairly safe now (oxymoronic, but true). Additionally, there are zero cases (so far) of incorrect detection of infinite loops and the rules associated, so those warnings definitely can help someone figure out what they did wrong.

• Fixed misaligned stack reporting, recursion stack acts more like a bin in than a stack now, forcing back-rolling up all candidates in a detected infinite-loop, rolled out tests and adapted to match existing warno-tests.
• Widespread spelling fixes, and light fixes to documentation.

All-intended-features release as 'postcss-extend'

Only known ongoing issues of note are some odd results (not even crashes, just results) when it attempts to correctly process CSS that has infinite @extend loops when @media statements are involved.

So, don't expect infinite loops to go over smoothly?
Yes, you shouldn't be using them anyway.

Features added since postcss-simple-extend (aka: v0.3.x and earlier) :

• Works with silent '%' selectors
• Works with existing (real) rules at root
• Strict behavior of standard placeholder, and relaxed behavior of % (silent) classes
• Elimination of duplicate selectors on extended rules
• Removal of otherwise empty code blocks (from only-extension)
• Acts recursively (both directions thanks to 'living log' behavior, and selective-recursion)
• Targets sub classes and extends them with pseudo version of the extended
• Acts recursively on sub classes
• Finds it's exisiting sub classes (shared scope in media) and pulls declarations into them when possible
• If inside @media does a declaration pull for anything outside @media
• Correctly handles re-declarations, by ignoreing incoming via @extend (original overwrites)
• Order of naming remains a predicatable add-to-tail fashion, and follows vertical order, then recursion in priority
• Detects, and gives a trace of all rules that are part of an infinite loop of @extend recursion.