Allow generating OpenAPI spec pages using operationId

[jfconde-payrails]

Request: make it possible, via docs.json configuration, to customize how the slugs for OpenAPI endpoints are auto-generated, allowing users to select the operationId field instead of summary.

Context

Our organization is migrating our docs to Mintlify. We currently have a large OpenAPI spec documenting our public API, with almost a hundred endpoints.

Mintlify generates the URL paths or "slugs" of openAPI specs based on the summary attribute of the endpoints in the OpenAPI specs. An endpoint described as:

 "/entities": {
  "get": {
    "summary": "Search & list entities",
    "operationId": "listentities",
    ...
  },
  "tags": ["Entities"],
  ...
}

Generates the following urls inside our navigation:
<base url>/reference/entities/search-&-list-entities

Rationale

After consulting the docs and AI assistant, the suggested solution is using the x-mint (as described here) field. Our OpenAPI spec is auto-generated from source at its original repository, and we do not want to pollute that source with extraneous fields, such as x-mint. While we can/will automate the generation or duplication of this field using the operationId field, this adds an additional conversion step for our present API and every future OpenAPI spec we want to publish in Mintlify.

While solvable, exposing an alternative configuration field in docs.json, at api or navigation item level, would be a very valuable feature - in my opinion - also for any other OpenAPI Mintlify users.