chore: rename next to done

[ryhinchey]

the callback used in fastify plugins is called done throughout the docs; however, next is used in the Typescript type. This PR updates the type to be consistent with the documentation

Checklist

• [x ] run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• [ x] commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[giulianok]

@ryhinchey this is awesome! I personally don't really care how the parameter is being called in the application side, but it would be great to have consistency in the docs, examples, code, tests, etc.

Maybe this PR could be used to change all the next references to done? https://github.com/fastify/fastify/search?p=3&q=next. I found that tests and examples are also using next

[ryhinchey]

@giulianok yah I'm happy to do that in this PR if the fastify team is on board with a PR changing so many files :)

[Ethan-Arrowood]

I'm 👍 for consistency. I don't believe this is a breaking change since its just function arguments (which can be named anything).

[Ethan-Arrowood]

Haha so there seems to be no consistency throughout the repo, nice fix! How do other maintainers feel about this? Would you rather us use next instead?

[Eomm]

[mcollina]

lgtm

This is massive work, thanks.

LGTM

[RafaelGSS]

LGTM.

[jsumners]

I can't go through this line by line. But I'm on board.

[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.