Switch to ad hoc maintenance

[devinivy]

I propose we switch this module to ad hoc maintenance. Most modules in the hapi pal organization receive similar or equal treatment to each other. For example, when a new version of node or hapi is released, all modules are actively updated to remain compatible. Under "ad hoc maintenance" issues for those tasks would be created and PRs welcome, but the work wont actively be completed. When updates do occur they will be accepted if they stick with pal's standards and conventions.
This means that this module would receive looser maintenance and may not stay up to date with nodejs or hapi unless the community makes a point to keep it up to date. A note of this fact would display in the readme. The main factor leading to this decision is that this module hasn't received contributions, doesn't have any dependents, and receives very few downloads. If the module ends-up unmaintained it will likely be deprecated, and if it is maintained or becomes more popular then it could come out of ad hoc maintenance, so nothing is absolutely final here.