fix: Wrap hooks now correctly receive options passed by outer wrappers

[mbg]

I discovered this while working on octokit/plugin-retry.js#661, where there appeared to be no difference between (simplified):

octokit.hook.wrap("request", (req, opts) => req(req, opts));

and

octokit.hook.wrap("request", (req, opts) => req(opts));

I eventually realised that the argument to (in this case) req didn't matter at all and traced the issue down to this library, specifically https://github.com/gr2m/before-after-hook/blob/main/lib/register.js#L23-L25

Since the docs, tests, and examples, all show the options being passed to the wrapped function, I assume that this is not intentional. This PR fixes the problem so that only the outer-most wrapper gets the initial options object and the others get the arguments they are called with. I also added a test for this.

There is potentially the same issue in https://github.com/gr2m/before-after-hook/blob/main/lib/register.js#L13-L15 but I wasn't sure if maybe it was the intended behaviour there. If not, then the following would fix it:

    return name.reverse().reduce((callback, name) => {
      return register.bind(null, state, name, callback);
    }, method)(options);

[gr2m]

There is potentially the same issue in main/lib/register.js#L13-L15 but I wasn't sure if maybe it was the intended behaviour there. If not, then the following would fix it:

yeah I think this needs to be fixed as well, great catch 👍🏼 Can you update your PR?

[mbg]

@gr2m Done, and also added another test for that.