Add hook data cache service

Problem/Motivation

Drupal stores compiler-generated hook metadata in the hook_data key-value collection:

• hook_list
• packed_order_operations
• theme_hook_list
• preprocess_for_suggestions

The three consumers own overlapping loading and caching logic:

- ModuleHandler loads and caches hook_list plus packed_order_operations.
- ThemeManager loads and caches theme_hook_list.
- Registry separately reads theme_hook_list and preprocess_for_suggestions directly from key-value storage.

On a cold cache, both Registry and ThemeManager independently load theme_hook_list.

Steps to reproduce

Proposed resolution

Introduce a HookData service that owns the compiler-generated hook_data reads and the bootstrap cache entries.

Use two logical cache groups:

1. Module hook data: hook_list and packed_order_operations

2. Theme hook data: theme_hook_list and preprocess_for_suggestions.

ModuleHandler, ThemeManager, and Registry would use this shared service. The service keeps request-local copies, reads from cache.bootstrap first, and falls back to the key-value collection on a cache miss.

This should remove two database queries from the cold cache performance tests.

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet