* Add aws, azure, gcp auth to features

* Remove un needed dep

…mparison (#171)

This comes up when filtering on a nested field in a related collection. For example, where there is a relation from `comments` to `movie`:

```graphql
query {
  comments(where: {movie: {imdb: {rating: {_eq: 9.2}}}}) {
    text
    movie {
      title
      year
    }
  }
}
```

In this example no records are returned because `imdb.rating` is not in scope when during filtering where that `where` predicate is applied.

We already have logic in place to include columns in joins if they are needed for an expression. But that logic did not account for **nested** fields. This PR updates the query planner to recursively include nested fields as needed if they are used in expressions.

Queries with multiple sort criteria were applying criteria
alphabetically in the MongoDB query plan instead of in the order
specified in the incoming NDC query.

…#175)

We had a bug when selecting fields with names containing dollar signs or
dots, or when selecting fields using aliases containing those
characters. What happened is the mongodb query plan would produce a
stage like this:

```json
{
  "$replaceWith": {
    "foo.bar": "$title"
  }
}
```

The use of `"foo.bar"` leads to this error:

> MongoServerError: FieldPath field names may not contain '.'. Consider
using $getField or $setField.

The fix is, as the error suggests, to use the `$setField` operator which
takes a `field` argument that is not evaluated as an expression, and is
therefore allowed to contain arbitrary characters.

```json
{
  "$replaceWith": {
    "$setField": {
      "field": "foo.bar",
      "value": "$title",
      "input": "$$CURRENT"
    }
  }
}
```

But that leads to an issue when we want to select multiple fields: in
the first snippet the argument to `$replaceWith` was an object literal
where we could set multiple fields. OTOH `{ "$setField": { ... } }` is
an expression that produces an object with a single field, and does not
accept more keys. To select multiple fields with escaping we have to
nest calls to `$setField` for every selected field. For example,

```json
{
  "$replaceWith": {
    "$setField": {
      "field": "foo.bar",
      "value": "$title",
      "input": {
        "$setField": {
          "field": "year",
          "value": "$year",
          "input": {
            "$setField": {
              "field": "rated",
              "value": "$rated",
              "input": "$$CURRENT"
            }
          }
        }
      }
    }
  }
}
```

So that is what this PR does.