[Do at breaking change] Remove bundled icons in 1.x release

[interactivellama]

**If you are using IconSettings with sprites or paths, this will not affect you. **

• Icons not working correctly seem to an issue consumers run into often. Removal of this legacy feature will simplify library logic and make one single path forward.
• Removing the 400kb+ of icons inlined into the JS will simplify the dependency tree and make resources like https://www.npmjs.com/package/webpack-bundle-analyzer more accurate.
• IE11 support should be provided by https://github.com/jonathantneal/svg4everybody

This will is scheduled for the 1.0 release which will be within the 2018 calendar year.

CORS

As a work around for CORS issues, I am open to a <IconSettings noCategoryPath /> that would allow you to XMLHttpRequest in the sprite map into a div and then call #down instead of utility/sprite.svg#down if that would work for folks that need inlining currently. See CSS tricks for more details

[interactivellama]

@pixelprodotco Here is the roadmap issue on inline icon removal if you need to share it with your team or infrastructure.

[sudowork]

Adding a noCategoryPath option for handling sprite sheets loaded via AJAX and injected in the DOM could help us (when serving the sprites from a CDN). Currently, I have set all the ${category}Sprite props to ” “ to pass the truthy checks as a hack.