Clarify Sandbox endpoint separation: Path vs Webhook

[nithyav2017]

{Clarify Sandbox endpoint separation: Path vs Webhook}

• [ X] I've read the Contributor Guide and Code of Conduct.
• I've included unit or integration tests for your change, where applicable.
  - This change is scoped to the Sandbox project and does not affect runtime behavior or require tests.
• [X ] I've included inline docs for your change, where applicable.
  - Endpoint separation is documented via PathItemTypeAttribute and modularized in PatientEndpointService.
  - A sample JSON output document is attached to illustrate how standard path endpoints and webhook endpoints are distinguished in the OpenAPI schema.
  > Note: When webhook endpoints are separated from standard paths using metadata like PathItemType.Webhook , they may not listed in tools like Postman that rely on conventional OpenAPI path discovery.
• [ X] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
  -This PR addresses Allow the OpenApiOperation be placed as a Paths or a Webhook #64039 by clarifying webhook or path routing in the sandbox.

Summary of the changes (Less than 80 chars)
Clarify endpoint separation using PathItemType metadata.

Description

{Modularized patient-related endpoints into PatientEndpoinService.cs to clarify architectural separation between standard path routes and webhook routes using PathItemTypeAttribute. Attached a sample JSON output to illustrate how OpenAPI schema distinguishes these endpoints. }

Fixes #{#64039} (in this specific format)
appDocument.json

[nithyav2017]

Superseded by #64088 with corrected metadata handling