[Federation] invalid query is sent to federated service when original query contains aliases with fragments

When sending a query like

```graphql
query Test {
node(
nodeId: "WyJ0ZXN0IiwiMSJd"
) {
... on Device {
name
}
... on Catalog {
name: title
}
}
}
```

the following invalid query is forwarded by the gateway to the federated service:

```graphql
{ node(nodeId: "WyJ0ZXN0IiwiMSJdOGE0Il0=") { __typename ... on Device { name } ... on Catalog { name } } }
```

This should be

```graphql
{ node(nodeId: "WyJ0ZXN0IiwiMSJdOGE0Il0=") { __typename ... on Device { name } ... on Catalog { name: title } } }
```

So the information that a field `title` is being queried that should be _renamed_ to `name` is lost. Instead, the field `name` is being queried directly (which leads to an error in my case, since my type `Catalog` does not have a field `name`).

This seems to only happen if there is a second interface there (in this case: `Device`) that reads a field that really has the aliased name.

The issue provides a GraphQL reproduction but names no source files or tests. Start by tracing how the federation gateway transforms aliases across the Device and Catalog inline fragments before forwarding a query. Add regression coverage and verify that the forwarded query preserves `name: title` instead of sending an invalid direct `name` field.

Written by the indexing model from the issue text.