Fix hook encapsulation

[delvedor]

Back in #642 we have decided to not encapsulate onRoute and onRegister, almost two years after, the use of this hooks in our plugins has changed, and make this two hooks encapsulated is now the right choice.

Unfortunately, doing so will introduce a breaking change, since the behavior of those hooks will change slightly.

onRoute
The hook will be called asynchronously, in v1/v2 it's called as soon as a route is registered. This means that if you want to use it, you should register this hook as soon as possible in your code.

onRegister
Same as the onRoute hook, the only difference is that now the very first call will no longer be the framework itself, but the first registered plugin.

Fixes: #1970

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows Code of conduct

[mcollina]

code LGTM.

How much does this affect fastify-swagger?

[delvedor]

How much does this affect fastify-swagger?

cc @Eomm 😉

[delvedor]

How much does this affect fastify-swagger?

If you declare fastify-swagger as top level, there is no change, if you declare it in a nested plugin, you will get the swagger definition only for the routes declared at that level and below.

[delvedor]

I'll proceed and merge this one so I can continue the work on fastify-express.
If you have some additional feedback or concern, open an issue! :)

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.