[sroucheray]

Summary

Two small fixes in the schema table, both seen on a real API that uses oneOf and untyped
schemas. They are independent, one commit each.

1. Untyped schemas that only carry annotations are shown as any

getTypeInfo only returned any for a completely empty schema. As soon as an untyped
schema had a description, the table rendered {missing-type-info}:

filter:
  type: array
  items:
    description: A string, a number or a boolean   # no `type`

• Before: filter [{missing-type-info}]
• After: filter [any]

A schema that only has annotation keywords (title, description, example, examples,
default, deprecated, readOnly, writeOnly, externalDocs, x-*) is now any.
A schema with constraints but no type (e.g. minLength: 3) still reports a missing type.

2. A primitive option of a oneOf / anyOf takes one row instead of two

A primitive option (string, number, boolean...) was rendered as the OPT n badge row,
then a second row named Option n that repeated it before the type:

OPT 1
Option 1      string
OPT 2
Option 2      number

The badge (and the option title, if any) now sits in the key cell of the primitive row:

OPT 1         string
OPT 2         number

Titled options and untitled objects/arrays are unchanged: their header row carries the
description and hosts the children, so it is kept.

Tests

• tests/unit/schema-utils.test.js: getTypeInfo returns any for annotation-only schemas
  (including x-*), and still reports a missing type for { minLength: 3 }.
• tests/unit/schema-ast.test.js: untitled primitive options are unnamed, titled options and
  untitled objects keep their name.
• npm run test:unit (472 pass), oxlint --deny-warnings, oxfmt --check.
• Checked by rendering an OpenAPI file with the built bundle before and after
  (screenshots attached).

I did not run the e2e / visual suites, which may compare screenshots of the schema table.

[mrin9]

Thanks for taking this one on urself