feat(hooks): Refactor .params, .props and .defaults into hooks

[daffl]

This pull request is another refactoring that turns params, props and defaults into setContext.params, setContext.properties and setContext.defaults hooks. Performance appears to be about the same (or better when you do not use those hooks) with a more simplified API and smaller code base (client side bundle size reduced by ~20%). It can be used like this:

const { hooks, setContext } = require('@feathersjs/hooks');

const sayHello = async name => {
  return `Hello ${name}!`;
};

const wrappedSayHello = hooks(sayHello, [
  // Sets `context.name`
  setContext.params('name'),
  // Sets `context.enabled
  setContext.properties({
    enabled: true
  }),
  // Sets default name (if not available)
  setContext.defaults(context => {
    return { name: 'David' }
  }),
  async (context, next) => {
    console.log(context.arguments);
    await next();
  }
]);

(async () => {
  console.log(await wrappedSayHello('David'));
})();

Closes #36
Closes #38

[bertho-zero]

I think this PR is a regression:

As I say here #36 (comment) the hook manager assures us that what manages the parameters is always executed before the rest of the hooks, I cannot know context.params in a hook attached to the class level. (https://runkit.com/embed/ewg0wrcqlj8o)
It is a potential source of error depending on the order in which we call params, props and defaults. defaults should be after params.
It is no longer possible to know the name of the params before executing the function, it is an info which can be useful.

[daffl]

Yeah, you're totally right and I ran into this problem literally right away 🤦 I like having it as a hook though since it's more consistent, less code to maintain and it can be faster. Should we bring back the options again then?

const { hooks, middleware } = require('@feathersjs/hooks');

const sayHello = async name => {
  return `Hello ${name}!`;
};

const wrappedSayHello = hooks(sayHello, middleware([
  async (context, next) => {
    console.log(context.name);
    await next();
  }
], {
  params: ['name'],
  defaults: context => ({ name: 'Dave', params: {} }),
  properties: { method: 'Something' }
}));

This would register a standard hook that always runs first and initializes those properties.

[bertho-zero]

I'm fine with the options, it's probably the best solution