fix(core): execute middleware in topological order of module imports

[igrek8]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

Middleware registration does not respect DI module imports.

Given:

• Module A
  • Middleware A
  • Module B
    • Middleware B
• Module C
  • Middleware C

Resolution:

1. Middleware A
2. Middleware C
3. Middleware B

What is the new behavior?

Order of middleware registration is resolved by DI module imports as described by the community.

Resolution:

1. Middleware A
2. Middleware B
3. Middleware C

Middleware will run in the order that the modules are added to the imports array.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[kamilmysliwiec]

This would introduce a major breaking change. Modules are supposed to be sorted by distance

[kamilmysliwiec]

Resolution:

Middleware A
Middleware C
Middleware B

This is the expected behavior given that module C is closer to the root module than module B