fix(ng-doc/component-groups-generate processor): use path/outputPath specified in processing.api-docs
fix(utils/code): encode HTML entities

Previously, the encoding was allowing things like `&#10;` to be passed through
unencoded. This was leading to some issues in display.  The trade off is that
we can no longer specify unusual chars as HTML entities in our code blocks,
but this seems correct to me.
chore(package.json): release v0.9.4
Revert "fix(ng-doc/component-groups-generate processor): use path/outputPath specified in processing.api-docs"

This reverts commit f2c3776f8660ab92810e0b940e74a8c74180f755.

This caused a breaking change to the code, which is not wanted in 0.9.x
branch. The feature can be achieved without a breaking change.
fix(ng-doc/component-groups-generate): allow path/outputPath to be configurable

You can now configure the path and outputPath of the component groups documents.

See #50
chore(package.json): release v0.9.5
fix(ng-doc/example): allow output path & urls to be configurable.
added new optional config param for examples "processing.examples.outputFolderPath" to compliment the existing "processing.examples.outputFolder"
updated a couple of places that were using the folder path as the url path (by default they are the same)