bug: Enums in the HTTP API aren't rendered correctly in documentation

[SyntaxColoring]

Copied from #8006 (comment)...

There's some weirdness happening to our enums. Here's a snippet from our generated OpenAPI spec:

"SessionCommandSummary": {
    "title": "SessionCommandSummary",
    "required": [
        "id",
        "commandType",
        "status"
    ],
    "type": "object",
    "properties": {
        "id": {
            "title": "Id",
            "type": "string",
            "description": "Unique command identifier."
        },
        "commandType": {
            "title": "Commandtype",
            "anyOf": [
                {
                    "const": "addLabwareDefinition",
                    "type": "string"
                },
                {
                    "const": "aspirate",
                    "type": "string"
                },
...

The anyOf consts looks good, but, on /redoc...

(This example is from the response of GET {{hostname}}:31950/sessions/{{session_id}}/commands.)

I don't know if this is a /redoc problem or a Pydantic problem or what.

[SyntaxColoring]

Things to investigate:

• How other APIs represent enums in OpenAPI
• Whether using a newer version of Redoc/FastAPI fixes this
• Whether other documentation generators fix this

[SyntaxColoring]

This appears to have been resolved at some point.