Omit redundant _NoAutoPK and _NoPK OpenAPI schemas when request-body-strict is false

[aaronburtle]

Why make this change?

Closes #3260

What is this change?

When request-body-strict is set to false, the OpenAPI document was still generating separate _NoAutoPK and _NoPK component schemas for each entity. These schemas only differ from the base entity schema by excluding primary key fields, a distinction that is meaningless when the request body already allows additional properties. This made the generated OpenAPI document unnecessarily verbose and confusing for consumers.

The isRequestBodyStrict flag is now threaded through BuildPaths and CreateOperations so that POST/PUT/PATCH request body schema references point to the base entity schema when strict mode is off. The CreateComponentSchemas method now gates _NoAutoPK and _NoPK schema generation on strict mode, and its XML documentation has been updated to accurately describe both strict and non-strict behavior.

How was this tested?

• Integration Tests
• Unit Tests

Updated existing unit test RequestBodyStrict_False_OmitsRedundantSchemas (renamed from RequestBodyStrict_False_AllowsExtraFields) to verify that when request-body-strict is false:

• _NoAutoPK and _NoPK component schemas are not generated.
• The base entity schema is still present.
• POST/PUT/PATCH operations reference the base entity schema (not _NoAutoPK or _NoPK).

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.

[Copilot]

Pull request overview

Updates OpenAPI document generation to avoid emitting redundant request-body component schemas (_NoAutoPK/_NoPK) when request-body-strict is disabled, reducing OpenAPI verbosity and aligning with the runtime behavior described in issue #3260.

Changes:

• Plumbs runtimeConfig.IsRequestBodyStrict into path/operation generation so request body schema refs can vary by strictness.
• Skips generating _NoAutoPK / _NoPK component schemas when request-body-strict is false and instead references the base entity schema.
• Updates the existing OpenAPI integration test to assert the redundant schemas are not produced in non-strict mode.

Reviewed changes

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

File	Description
src/Service.Tests/OpenApiDocumentor/RequestBodyStrictTests.cs	Renames/updates the non-strict test to verify _NoAutoPK/_NoPK schemas are omitted and base schema remains.
src/Core/Services/OpenAPI/OpenApiDocumentor.cs	Threads request-body strictness into BuildPaths/CreateOperations and gates request-body schema generation on strict mode.

[aaronburtle]

@copilot can you please review again

[Copilot]

@copilot can you please review again

Both previously flagged issues have been addressed in the existing commits:

1. Test assertions (commit fc72502): RequestBodyStrict_False_OmitsRedundantSchemas now iterates through all path operations and asserts that POST/PUT/PATCH request bodies reference the base book schema, not book_NoAutoPK/book_NoPK.

2. XML doc on CreateComponentSchemas (commit afd7ae7): Updated to accurately document that when isRequestBodyStrict is false, only the base {EntityName} schema is created and all request body operations reference it directly.

The implementation is complete and no further changes are needed.