refactor to leverage hapi plugin options

First of all, thanks for this and for AmpersandJS :)

This PR makes this module conform a bit more to hapi plugin conventions. instead if dynamically creating plugins via a factory, it instead leverages the `options` argument when registering the plugin to pass in the dummy data/config object. It also specifies `multiple: true` in the plugin attributes to allow the plugin to be registered multiple times.

I realize that this PR touches 60% of the code, and I understand that it fundamentally changes the way the dummy APIs are created and registered. If this proposed convention does not suit your tastes, feel free to reject this PR... no hard feelings, I can always fork :)