Rename AI tool function names to the eb_ prefix

Problem/Motivation

The AI tools shipped by entity_blueprint_ai and entity_blueprint_config_ai used verbose, module-prefixed function names such as entity_blueprint_config_manage_plugin_collection. These names are LLM-facing: they are the identifiers a model calls and the strings that appear in every tool schema and in inter-tool guidance text. The long names cost tokens, read inconsistently, and make cross-references in tool descriptions harder to scan.

Proposed resolution

Move every tool function_name into a short, consistent eb_ namespace (eb_ for content tools, eb_config_ for config tools), and update tool descriptions and the EntityBlueprintToolBase guidance message to reference the new names and the eb_skill / eb_list_bundles discovery workflow.

Plugin IDs (the id: key, e.g. entity_blueprint:create_entity) are unchanged; only the LLM-facing function_name values change.

API changes

Backward-incompatible. The function_name is the identifier exposed to the model and the string by which ai_agents.ai_agent.* and ai_assistant_api.ai_assistant.* tool allow-lists reference these tools. Any agent/assistant configuration that enables these tools by name must be updated to the new eb_ names, or the tools will no longer be available to that agent. The module is lifecycle: experimental, so the rename ships without a deprecation path.