Add an @inline direction in client-preset to unmask actual GraphQL fragments

### Is your feature request related to a problem? Please describe.

A user may have prior-existing fragments, or want to use fragments, that are not 1:1 directly associated with a specific component. For example:

```
fragment User {
id
name
...
}

query {
user(...) {
...User
}
}
```

With the current fragment masking in `client-preset`, these fragments are assumed to be components, which will then fail to work.

### Describe the solution you'd like

My suggestion is to mirror how Relay is designed, with an `@inline` or `@relay(mask: false)` directive. This directive indicates that a fragment is _not_ a component's fragment and allows intermixing of actual fragments with component fragments:

```
query {
user(...) {
...UserAvatar_User
...User @inline
}
}
```
this will expand the `User` fragment, but continue to mask the `UserAvatar_User` fragment (which might itself want to expand the `User` fragment)

### Describe alternatives you've considered

One alternative is to simply suggest that fragments themselves are an antipattern because repeated GraphQL entire objects should be abstracted to a component. I think this is an unrealistic approach, especially when considering transitioning onto fragment masking from an existing codebase.

### Is your feature request related to a problem? Please describe.

_No response_