AddMaxExecutionDepthRule doesn't work properly when used after AddMaxComplexityRule

Describe the bug AddMaxExecutionDepthRule doesn't calculate depth, but uses complexity, if it's added to the service collection after AddMaxComplexityRule.

To Reproduce Steps to reproduce the behavior:

Use the following configuration in ConfigureServices

services.AddGraphQLServer()
...
.AddMaxComplexityRule(20)
.AddMaxExecutionDepthRule(5);

Send a query on a single depth level, but with complexity higher than 5 Example:
```
query {
user {
id
firstName
email
createdAt
updatedAt
}
}
```

Received this response

{
"errors": [
{
  "message": "The GraphQL document has an execution depth of 6 which exceeds the max allowed execution depth of 5.",
  "locations": [
    {
      "line": 1,
      "column": 1
    }
  ],
  "extensions": {
    "allowedExecutionDepth": 5,
    "detectedExecutionDepth": 6
  }
}
]
}

Expected behavior When I swapped the position of AddMaxExecutionDepthRule and AddMaxComplexityRule the issue was solved. If that's expected to happen, I think it'll be best to update the documentation (searched the whole documentation for both v10 and v11 and found nothing about this).

Fixed code example:

services.AddGraphQLServer()
  ...
  .AddMaxExecutionDepthRule(5)
  .AddMaxComplexityRule(20);

Desktop (please complete the following information):

OS: macOS
Version: 11.4

Additional context .NET SDK (5.0.301) HotChocolate.AspNetCore: 11.3.0 HotChocolate.AspNetCore.Authorization: 11.3.0 HotChocolate.Data.EntityFramework: 11.3.0 HotChocolate.Subscriptions.Redis: 11.3.0 HotChocolate.Types.Scalars: 11.3.0

ChilliCream / graphql-platform

AddMaxExecutionDepthRule doesn't work properly when used after AddMaxComplexityRule #3840