Issue #3612365: Rename the booking entity type from yoyaku to yoyaku_booking

Frank Mablyrequested to merge
issue/yoyaku-3612365:3612365-rename-the-booking into 1.x

Renames the booking line entity type id (and its base table) from yoyaku to yoyaku_booking, so it follows the yoyaku_* naming every sibling entity uses (yoyaku_resource, yoyaku_slot, yoyaku_transaction, ...) and is no longer ambiguous with the module machine name.

Context-aware rename across ~40 files: entity-id contexts (getStorage, installEntitySchema, entity-type-id strings/keys, Action plugin type, raw table references in queries, storage-schema index names yoyaku__* to yoyaku_booking__*, the views base_table/table, the entity:yoyaku route parameter) all move to yoyaku_booking; module-name contexts (module install, test $modules / installConfig, test groups) stay yoyaku.

Pre-1.0, no update hook: the live table and its indexes are renamed by hand on deploy.

Split from #3612196.

Merge request reports