feat(types): add middlewares types

[thib3113]

Add typing for the optionals middlewares

PS : I typed the encryption middleware too, but I think it's not a good middleware, not secure (IV not changing), and hard to use (password length need to be a strict length)

💎 Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

🏁 Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have commented my code, particularly in hard-to-understand areas

[shawnmcknight]

A couple things here:

1. What's the use case for making this change?
2. Although there are many places in the existing types where namespace is used, its a pattern I'd prefer to avoid in the future. Can the changes you're making be accomplished without using them?
3. Types should always be PascalCase and not camelCase. There are several changes here using camelCase.

[thib3113]

@shawnmcknight

1. What's the use case for making this change?

It allow to add middleware in moleculer.config.ts, without using ts-ignore

2. Although there are many places in the existing types where namespace is used, its a pattern I'd prefer to avoid in the future. Can the changes you're making be accomplished without using them?

I will check

3. Types should always be PascalCase and not camelCase. There are several changes here using camelCase.

Ok, I will check

[thib3113]

when I want to use the middleware in my moleculer.config.ts now :

[thib3113]

@shawnmcknight any news on this ?

[shawnmcknight]

Overall this looks good. I had a few requests for adjustment.

[thib3113]

Please @shawnmcknight / @icebob can you review this PR ? it is waiting for nearly a year, where PR #1246 with same changes was validated in 2 days (litterally the PR just re-do a part of this one) ...