Capabilities API

[onx2]

Summary

Move table capability registration into the table subsystem while preserving the existing high-level APIs.

Capability-based registration is now available for cases where the source type does not fully describe the desired bindings:

.bind::<PlayerTableAccessor>([
    TableCapability::insert(),
    TableCapability::delete(),
    TableCapability::update(),
    TableCapability::insert_update(),
])

Direct convenience methods are also supported:

.bind_insert::<PlayerTableAccessor>()
.bind_delete::<PlayerTableAccessor>()
.bind_update::<PlayerTableAccessor>()

Capabilities are checked at compile time through WithInsert, WithDelete, and WithUpdate. For example, binding delete or update to an event table fails to compile.

Existing APIs such as add_table, add_view, and add_event_table remain available for higher-level setup. Duplicate accessor/capability registrations fail at configuration time with a precise error message.