[jacoblambert]

Summary

Registers the 1.0 table classes by name, so the loader (next PR) can build every table without a hard-coded list.

• t4_devkit/schema/v1/name.py: SchemaName for the 1.0 tables (no calibrated_sensor, surface_ann; adds vehicle, route, scenario, caption), with filename and is_optional(). Required tables: sample, sample_data, ego_pose, sensor, scene, log, vehicle.
• t4_devkit/schema/v1/registry.py: a 1.0 SCHEMAS registry. Every 1.0 class registers itself with @SCHEMAS.register(SchemaName.X), as the 0.x tables do.

Change to existing code

SchemaRegistry (t4_devkit/schema/tables/registry.py) takes the name enum it accepts as an argument, instead of only the 0.x SchemaName. The default is the 0.x enum, so existing code and the 0.x SCHEMAS are unchanged. Each registry rejects names from the other version.

Tests

tests/schema/v1/test_registry.py:

• Every 1.0 table name has a registered class, and filenames are <name>.json.
• The required tables match the spec.
• The 0.x and 1.0 registries only accept their own names.
• A table class can be replaced with force=True, as documented for 0.x.

[ktro2828]

LGTM