Fix for nested addons

If you have been having trouble with using this package with nested addons, linked addons, or the like, please try to upgrade to version 0.6.9 of all packages to see if this is able to mitigate your issue.

The fix for this isn't an ideal fix, but it is stable enough that I feel comfortable releasing it. Please see PR 317 for more details.

Package Upgrades

All dependent packages have now been upgraded to their latest version, and the tests have been fixed.

styleNamespace

moving away from componentCssClassName and to styleNamespace. It's clearer, simpler, and speaks more to what it's use case is. componentCssClassName is still able to be used for the time being, and in a later version will add in a depreciation when it is used.

Route Namespacing

Enabling namespacing of routes via a class list property on the application controller called routeStyleNamespaceClassSet and on an individual controller of styleNamespace. See useage with routes for more info on how to use.

v0.3.0

Moved the main initializer into the app space, and added an mixin for better extensibility of the component identifiers.

v0.2.12

SCSS @ for rules are now no longer pulled out into the root, and are scoped by the namespace.

v0.2.11

Classic structure support! Much thanks to @john-griffin for bringing this in for the whole community! 🎉

v0.2.9

Improved support for usage in addons that use a different css preprocessor then the parent app.

v0.2.8

Updated to the new getOwner polyfill. thanks @charlesdemers

v0.2.7

No longer name spacing children of @ rules except @media and @supports