feat: configurable broadcasts + /core reload

New fr.luc.crcore.broadcast module:
- BroadcastAudience enum (NONE, LEADER, TEAM, ADMIN, ALL).
- BroadcastContext (fluent: team + involvedPlayerId + placeholders).
- BroadcastService interface + YamlBroadcastService impl.
- CRCoreBroadcastListener (Bukkit listener) wires the 12 native events
  (9 team + 3 player) to broadcasts.broadcast(eventKey, ctx).

Same single-per-plugin file pattern as messages:
<plugin-dataFolder>/<plugin-name-lowercase>-broadcasts.yml. Defaults
bundled at resources/crcore-broadcasts.yml, copied on first boot (game
plugin's own resource of the same name takes priority as the template).
In-memory fallback so new CR-Core keys work without admin edit.

Routes (who) vs templates (what) are separated: broadcasts.yml lists
audiences per eventKey, messages.yml contains the templates under keys
<eventKey>.broadcast. Admin can change either independently.

12 new *.broadcast keys added to crcore-messages.yml with sensible
French defaults and color codes. Listener injects standard placeholders
(name, team_name, tag, color, visibility, player, new_leader,
old/new_value, etc.).

ADMIN audience resolved via crcore.broadcast.admin permission. Multi-
audiences via YAML list (e.g., [TEAM, ADMIN]); union of resolved
players, no duplicate.

New /core reload subcommand (permission crcore.reload) hot-reloads
both messages and broadcasts from disk without restart.

CRCore: protected buildBroadcastService() override point, getter
broadcasts(), wire of CRCoreBroadcastListener at enable(). CoreCommand
constructor extended to take BroadcastService, registers the reload
subcommand.

Docs/features.md: new section 9 "Service de broadcasts". docs/setup.md:
updated to mention both YAML files. decisions.md logs the routes-vs-
templates split, the audience model, and the reload semantics.
New diagram broadcasts-class-diagram.puml. README updated.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

docs/README.md

@@ -30,6 +30,12 @@ d'initialisation côté plugin de jeu :
   YAML `<plugin>-messages.yml` dans le dataFolder du plugin de jeu,
   avec defaults CR-Core en fallback. L'admin édite un seul fichier,
   placeholders nommés, codes couleur `&` natifs.
+- **Broadcasts configurables** — `BroadcastService` route chaque event
+  CR-Core vers une liste d'audiences (`NONE`, `LEADER`, `TEAM`, `ADMIN`,
+  `ALL`) définie dans `<plugin>-broadcasts.yml`. Séparation routes /
+  templates. Un listener interne wire les 12 events natifs ; les game
+  plugins peuvent broadcast leurs propres events. `/core reload` recharge
+  les deux fichiers à chaud.
 - **Bootstrap unique** — `new CRCore(this).enable()` dans le `onEnable()`
   du plugin de jeu, et tout est branché.
 
@@ -55,6 +61,7 @@ d'initialisation côté plugin de jeu :
 | [events-diagram.puml](diagrams/events-diagram.puml) | Classe | Évènements Bukkit team + player |
 | [database-diagram.puml](diagrams/database-diagram.puml) | Classe | Wrapper SQLite + table builder |
 | [messages-class-diagram.puml](diagrams/messages-class-diagram.puml) | Classe | Service de messages YAML |
+| [broadcasts-class-diagram.puml](diagrams/broadcasts-class-diagram.puml) | Classe | Service de broadcasts YAML + listener |
 | [bootstrap-sequence.puml](diagrams/bootstrap-sequence.puml) | Séquence | `CRCore.enable()` côté plugin de jeu |
 
 ## Conventions