[8.x] Use parents to resolve middleware priority

[netpok]

Currently when middlewares are ordered it uses the class name and its interfaces for sorting but not it's parents.

This is a problem for example in Jetstream because:

• Jetstream extends the AuthenticateSession middleware with it's own.
• Since it doesn't have a contract it will run before any Authenticate middleware
• Resulting in it's always being initialized via the default guard instead of the authenticated one
• This prevents using two guards simultaniously (for example a user and an admin guard)

This PR fixes this behaviour by using parent classes for ordering so the Jetstream AuthenticateSession middleware will be in the correct place because it extends the Laravel AuthenticateSession middleware.

I also added test for the parent sorting and the already present interface sorting.

[driesvints]

We're going to have to revert this: 404labfr/laravel-impersonate#145 & #39705

[netpok]

@driesvints I'm pretty sure the package has some bugs in it but probably it's best to revert it and I will target 9.x later if I have some time

[driesvints]

@netpok as said in the other thread: it would be good if we could identify the bug itself so we know how this will impact others.