avoidOptionals inputValue as false not producing optional fields

**Describe the bug**

In the following live demo:

- observe an optional GQL query input, `userId: ID`
- you can see that we are `avoidOptionals: { inputValue: false }` for that value
- the output **does avoid** optionals, despite being instructed _not to_. you can see the following output:


```ts
export type FindUserQueryVariables = Exact<{
userId: Maybe;
}>;
```

Interestingly, if you flip `object: false` as well, suddenly the correct behavior takes for `inputValue: false`. Perhaps these are unintentionally coupled?

https://www.graphql-code-generator.com/docs/plugins/typescript-operations

**To Reproduce**

Codesandbox has been down for me. The schema, query, & config are listed below. The repro is quite simple :)

1. My GraphQL schema:

Stripped down version of the homepage demo:

```graphql
schema {
query: Query
}

type Query {
user(id: ID): User
}

interface Node {
id: ID!
}

type User implements Node {
id: ID!
}
```

2. My GraphQL operations:

```graphql
query findUser($userId: ID) {
user(id: $userId) {
id
}
}
```

3. My `codegen.yml` config file:

```yml
generates:
operations-types.ts:
plugins:
- typescript
- typescript-operations
config:
avoidOptionals:
defaultValue: true
field: true
object: true # toggle me!
inputValue: false

```

**Expected behavior**

To produce an optional value for the `userId?: Maybe` field:

**expected**:

```ts
export type FindUserQueryVariables = Exact<{
userId?: Maybe;
}>;
```

**actual**:

```ts
export type FindUserQueryVariables = Exact<{
userId: Maybe;
}>;
```

**Environment:**

latest, deployed on graphql-code-generator website

**Additional context**

This PR https://github.com/dotansimha/graphql-code-generator/pull/5113, in the bottom comment, seems to suggest that this design is intentional. However, `object` seems orthogonal to `inputValue` for `avoidOptionals` configuration, and produces an unexpected result. If they are not orthogonal, then `inputValue` should take precedence over `object`