Improve GraphQL naming conflict error to identify conflicting entities and operations

[Copilot]

Why make this change?

When autoentities includes tables whose names differ only by singular/plural form (e.g. dbo.Category and dbo.Categories), DAB fails startup with a vague error that doesn't identify the other conflicting entity, the generated GraphQL names, or how to resolve the conflict.

What is this change?

• RuntimeConfigValidator.ValidateEntitiesDoNotGenerateDuplicateQueriesOrMutation: Replaced HashSet<string> operation tracking with Dictionary<string, string> (operation → owning entity). Checks all operations (not short-circuit) to collect every conflicting name, then builds a structured error message including:
  • Both conflicting entity names
  • Singular/plural type names (for table/view entities)

Before:

Entity dbo_Category generates queries/mutation that already exist

After:

GraphQL naming conflict detected.

Entities:
  dbo_Categories
  dbo_Category

Both entities generate the following GraphQL names:
  Singular type: Category
  Plural type: Categories

Configure distinct GraphQL singular and plural names for one of the entities to resolve this conflict.

How was this tested?

• Integration Tests
• Unit Tests
  • Updated ValidateExceptionForDuplicateQueriesDueToEntityDefinitions helper to verify both conflicting entity names appear in the message
  • Updated all 6 existing duplicate-detection test call sites
  • Added ValidateAutoEntitiesWithSingularPluralNameCollisionGenerateDuplicateQueries covering the exact dbo.Category / dbo.Categories scenario

Sample Request(s)

N/A — error message improvement only; no API behavior changes.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[RubenCerna2079]

Copilot Change the PR so that in the output message we don't include the operation names. Also, if possible we want to keep using the hashset we already used before. Try to change the logic as little as possible from what it was before the changes you made in this PR. The only change should be the error message.

[Copilot]

Copilot Change the PR so that in the output message we don't include the operation names. Also, if possible we want to keep using the hashset we already used before. Try to change the logic as little...

Done in 3a1f2d0. The changes are now minimal:

• Reverted back to HashSet<string> with the original bool containsDuplicateOperationNames flag and || short-circuit chain
• Added a parallel Dictionary<string, string> operationOwner (only used for error reporting) to identify which entity previously registered the conflicting operations
• The error message now shows both conflicting entity names but no operation names

New message format:

GraphQL naming conflict detected.

Entities:
  dbo_Categories
  dbo_Category

Configure distinct GraphQL singular and plural names for one of the entities to resolve this conflict.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-pipelines]

Azure Pipelines:
Successfully started running 6 pipeline(s).

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 6 pipeline(s).

[aaronburtle]

Looks good once comments are addressed!

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 6 pipeline(s).

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 6 pipeline(s).

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 6 pipeline(s).

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 6 pipeline(s).

[RubenCerna2079]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 6 pipeline(s).