feat: Feathers v5 core refactoring and features

[daffl]

I'm not a huge fan of single massive PRs especially if they will break things but it turned out that there wasn't really a way around it since some of the changes were pretty substantial and overarching. Overall documented API usage is mostly backwards compatible. Breaking changes are being documented in the v5 migration guide.

This pull request addresses several long standing feature request and issues broken down as follows:

Asynchronous application initialization

app.setup and app.listen are now asynchronous. This allows to initialize databases, connections and can be combined with the new @feathersjs/hooks for more complex workflows.

• Closes Asynchronous initialization of Feathers services #509
• Closes app.setup() should be async #853

Custom methods

This lays the groundwork for custom methods laid out in #1976 but still needs tests.

Asynchronous middleware with @feathersjs/hooks

This pull request builds on top of @bertho-zero's work and should finalize the migration to the new asynchronous @featherjs/hooks. It contains a backwards compatible wrappers for before, after and error service and application hooks but makes asynchronous hooks a first class citizen.

• Closes Asynchronous initialization of Feathers services #509
• Closes Koa style middleware: Hooks for any asynchronous method #932
• Closes [FR] Support reverse application hooks #1548
• Closes Running a global hook after service hooks #1723

This also allows improved error handling, including better stack traces.

• Closes FeathersError stripped of dynamic properties in Winston logger #1160
• Closes Error format #1262
• Closes Errors result in GeneralError without specifics of the cause #1274

TypeScript improvements

Also included are major TypeScript improvements which should also allow better usability and code completion in editors like VSCode for non-TypeScript users.

• Typed app.get and app.set
• Improved application service declaration
• Fully typed hook context including proper application and service type
• Individual service request and response types

Addresses the following issues:

• Closes RFC: add support for Service Request and Response type #2125
• Closes Feathers v4 upgrade declarations file missing #1738
• Closes Sequelize and upgrading to feathers V4 with TypeScript #1736
• Closes Feathers V4 Typescript: Typed hookContext example #1741
• Closes How to make context.app.service('service-name') Typed? #1742
• Closes Feathers Typescript - Typed HookContext #1952
• Closes feathers service declaration #2005
• Closes Hook typing and find method parsing issue #2147
• Closes Typescript Quick Start example has type errors #2228

[ismail-codinglab]

Damn that's one hell of a typescript improvement, no more wild guesses or lots of any workaround. 👍 🥳

I don't mind this being a big pr as long as it's covered by tests, which it look like it is.

Do you know when or in which version/tag this will be available?

Again thanks for all that you do to make our lives easier