[CosmosDB_NoSQL] Validate GraphQL type name in schema.gql matches singular type name in config for the same entity

[Aniruddh25]

I agree its an edge-case scenario - perhaps, should fail in validation if GraphQL type name from schema.gql doesn't match the singular type name provided for the same entity as described by the model name directive in the schema.

Originally posted by @Aniruddh25 in #1402 (comment)

[aaronpowell]

To expand on this scenario a little more (from working through a regression in #1402), there are three places that the "name" of an entity can be configured for Cosmos DB:

• The RuntimeConfig.Entities collection
• The @model directive
• The GraphQL object type name

There is then another layer of potential confusion that can be layered on here by using custom singular/plural names in the config.

As a result, this is a valid way to define everything:

type Foo @model(name: "Bar") {
  id: String!
}

{
  "entities": {
    "Bar": {
      "source": "db.xzy",
      "graphql": { "singular": "baz" }
    }
  }
}

(I've dropped some of the config for simplicity here).

Based on the above:

• What is the name of the Object Type exposed for queries and mutations in GraphQL?
• What is the name in the _by_pk query?
• What is the name in the mutations?
• What is the name of the collection that the entities are stored?

The result of this is really quite confusing, as you get the following queries and mutations:

type Query {
  baz_by_pk(...): Foo
  bars(...): FooConnection
}

type FooConnection {
  items: [Foo!]
}

type Mutations {
  createBar(...): Foo
  updateBar(...): Foo
  deleteBar(...): Foo
}