Improve frontend devs data experience

[mcdonnelldean]

People working on the frontend need to have an up to date data reference to work from. With this in mind I think we need the following actions.

Add sample calls and data to readme's

@matt-oc please make an issue on npm, github, travis. This issue asks to update the readme with sample data from each response. The expectation is each pattern in handled and emitted section will have some sample code on how to call the pattern and a sample result that gives people a solid idea of what to expect in cases of a valid response. Assign these issues between yourself @CodeWriterWriter and @shanel262 and @powerbrian

Add Isolated Mode to npm and travis

Add isolated mode to Travis and Npm. This is already been done in Github. For ports us 8053 for travis and '8051' for npm. @matt-oc please make issues for these and assign them myself. Adding isolated mode will allow designers to npm run isolated and test what data comes back easy

Use mem-store in Isolated Mode

We have added redis for hard caching in npm, travis and github. In Isolated mode this is an additional uneeded overhead. We have a flag that can control the mode we are in. When in isolated mode we should not load the redis store plugin. This will instead use mem-store and not require additional infrasturcture to be ran. @CodeWriterWriter can you make an issue on each library (npm, travis, github) nothing this so we can assign it out to people later?

[matt-oc]

@mcdonnelldean will do 👍