Schema with multiple enum generates unusable data class

[choweiyuan]

Library Version
What version are you using?
4.0.0-rc1

Describe the bug
When I have a schema that contains multiple enums, then the client generates a class that does not work (due to ambiguity). If I comment out one of the enum imports it compiles fine.

To Reproduce
Steps to reproduce the behavior. Please provide:

Kotlin code to generate schema:
Similar to this as I'm referencing local schema.graphql and query.graphql #1104

Schema

schema {
  query: Query
  mutation: Mutation
}

type BudgetDataView {
  provider: Provider!
  status: Status!
}

enum Provider {
  PROVIDER_A
  PROVIDER_B
  UNKNOWN
}

enum Status {
  FOUND
  INTERNAL_ERROR
  NOT_FOUND
}

type Query {
  fetchBudgetData: [BudgetDataView!]!
}

Query

query FetchBudgetDataQuery {
  fetchBudgetData {
    provider
    status
  }
}

Expected behavior
A working data class, for example:

package com.company.project.graphql.provider.fetchbudgetdataquery

import com.company.project.graphql.provider.BigDecimal
import com.company.project.graphql.provider.Instant
import com.company.project.graphql.provider.enums.Provider
// Don't need this? since enums.Provider is imported
//import com.company.project.graphql.provider.enums.Provider.__UNKNOWN_VALUE
import com.company.project.graphql.provider.enums.Status
// Don't need this either?  since enums.Status is imported.
//import com.company.project.graphql.provider.enums.Status.__UNKNOWN_VALUE
import kotlin.String

public data class BudgetDataView(
  public val provider: Provider = Provider.__UNKNOWN_VALUE,
  public val status: Status = Status.__UNKNOWN_VALUE,
)