[DMS-753] Placing the extension in the right place when Core and Extension have…

[JBrenesSimpat]

The change consists of placing the extension in the right place when Core and Extension have the same property (sample extends it).
The following resources were successfully compared against ODS Stage (via Swagger: https://stage.preview.ed-fi.org/v7.3/docs/swagger/index.html?urls.primaryName=Resources):

• 'EdFi_Contact'
• 'EdFi_Credential'
• 'EdFi_School'
• 'EdFi_Staff'
• 'EdFi_StudentCteProgramAssociation'
• 'EdFi_StudentContactAssociation'
• 'EdFi_StudentEducationOrganizationAssociation'
• 'EdFi_StudentSchoolAssociation'
• 'EdFi_StudentSectionAssociation'
• 'EdFi_Student'
• 'EdFi_SurveyResponse'

[Copilot]

Pull Request Overview

This PR refactors the OpenAPI extension processing logic to correctly handle cases where core and extension schemas have the same property names. The refactoring introduces a new approach that analyzes property conflicts and redirects extension properties to their appropriate referenced schemas when conflicts occur.

Key changes include:

• Introduction of sophisticated property conflict detection and resolution logic
• Addition of multiple helper methods to handle complex extension scenarios
• Enhanced validation and error handling for extension schema processing
• Backward compatibility preservation for simple extension formats

Reviewed Changes

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

File	Description
OpenApiDocument.cs	Major refactoring of extension processing with new conflict resolution logic and helper methods
OpenApiDocumentTests.cs	New test suite to verify backward compatibility and refactored functionality

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}