Eliminate code duplication requests between Upsert and Insert

[aaronburtle]

Why make this change?

Closes #3209

What is this change?

Allow Upserts coming from REST requests to fall through to the Insert logic when auto-generated primary keys are missing. This eliminates code duplication between these two ops in the SqlMutationEngine

Add a test to cover the case when we have a PUT/PATCH with keys provided in the request body.

How was this tested?

New test was added to ensure complete coverage over the scenarios introduced with the keyless PUT/PATCH change.

Sample Request(s)

PUT that updates existing row (expects 200 OK):

PUT https://localhost:5001/api/magazine
Content-Type: application/json

{
    "id": 1,
    "title": "Updated Vogue",
    "issue_number": 9999
}

PUT that inserts new row (expects 201 Created):

PUT https://localhost:5001/api/magazine
Content-Type: application/json

{
    "id": 5001,
    "title": "Brand New Magazine",
    "issue_number": 42
}

PATCH that updates existing row (expects 200 OK):

PATCH https://localhost:5001/api/magazine
Content-Type: application/json

{
    "id": 1,
    "title": "Updated Vogue"
}

PATCH that inserts new row (expects 201 Created):

PATCH https://localhost:5001/api/magazine
Content-Type: application/json

{
    "id": 5001,
    "title": "Brand New Magazine"
}

[aaronburtle]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[aaronburtle]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[Copilot]

Pull request overview

This PR updates SQL mutation handling so REST upserts (PUT/PATCH) without a PK in the route can reuse the existing insert/update flow: if PKs are absent it behaves like an insert, and if PKs are supplied in the body it can correctly update an existing row. It also adds regression tests to cover keyless PUT/PATCH requests where PKs are provided in the request body.

Changes:

• Promote primary key values from request body into PrimaryKeyValuePairs for keyless upsert requests when all PK fields are present.
• Treat keyless upsert requests that still lack PKs as effective inserts to avoid generating unsafe UPDATE statements.
• Add cross-DB REST tests for keyless PUT/PATCH upsert behavior when PKs are included in the body.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/Service.Tests/SqlTests/RestApiTests/Put/PutApiTestBase.cs	Adds PUT regression tests for keyless routes with PKs in body; minor comment line touched.
src/Service.Tests/SqlTests/RestApiTests/Put/PostgreSqlPutApiTests.cs	Adds SQL verification queries for new PUT tests (PostgreSQL).
src/Service.Tests/SqlTests/RestApiTests/Put/MySqlPutApiTests.cs	Adds SQL verification queries for new PUT tests (MySQL).
src/Service.Tests/SqlTests/RestApiTests/Put/MsSqlPutApiTests.cs	Adds SQL verification queries for new PUT tests (SQL Server).
src/Service.Tests/SqlTests/RestApiTests/Patch/PatchApiTestBase.cs	Adds PATCH regression tests for keyless routes with PKs in body.
src/Service.Tests/SqlTests/RestApiTests/Patch/PostgreSqlPatchApiTests.cs	Adds SQL verification queries for new PATCH tests (PostgreSQL).
src/Service.Tests/SqlTests/RestApiTests/Patch/MySqlPatchApiTests.cs	Adds SQL verification queries for new PATCH tests (MySQL).
src/Service.Tests/SqlTests/RestApiTests/Patch/MsSqlPatchApiTests.cs	Adds SQL verification queries for new PATCH tests (SQL Server).
src/Core/Resolvers/SqlMutationEngine.cs	Refactors upsert flow so keyless upserts either use body PKs for UPDATE or fall through to INSERT path.

[aaronburtle]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).