Preserve Original Schema Field Order in API Developer Portal UI

Description:

Currently, schema fields displayed in the API Developer Portal appear to be automatically sorted in alphabetical order. This behavior alters the original structure of the schema and creates confusion for consumers who expect the fields to be presented in the same sequence as defined by the API specification.

Current Behavior:

Schema fields are displayed alphabetically in the Developer Portal UI.
The displayed field order does not match the order defined in the source schema/OpenAPI specification.

Expected Behavior:

The Developer Portal should preserve and display schema fields in the exact order they are defined within the source schema.
Any nested objects and arrays should also maintain their original field sequence.

Business Impact:

Improved readability and usability of API documentation.
Consistent representation of API schemas across design and consumption layers.
Reduced confusion for API consumers when comparing portal documentation with the original schema definitions.
Enhanced developer experience and documentation accuracy.

Use Case: When API consumers view request or response schemas in the Developer Portal, they should see the fields in the same order as defined by the API designer. This helps users follow business processes and data structures more intuitively, especially for large and complex schemas.

Requested Enhancement: Modify the API Developer Portal UI rendering logic to retain and display schema properties in their original definition order instead of automatically sorting them alphabetically.