style(reforcexy): harmonize all log/error message prefixes to '<Component> [<scope...

style(reforcexy): harmonize all log/error message prefixes to '<Component> [<scope>]:' (#264)

Exhaustive audit of ReforceXY.py messages: 144/148 now follow the
dominant '<Component> [<scope>]:' convention.

Ported (QuickAdapter PR #261) messages reprefixed:
- Training [%s]: cannot continue / continuing deployment / RL
  preprocessing / model-on info log / warmup (Live [%s]:).
- Training banners converted to 'Training [%s]: starting|completed'
  (were asymmetric '----Starting/done training----' separators).

Pre-existing non-scoped messages reprefixed:
- Repair [global]: FreqAI prediction repair synchronous-drawer guard.
- Journal [%s]: corrupt-journal quarantine warning.
- Hyperopt [global]: best-params lock/path filesystem invariants.

Remaining 4 are by-design, not user-facing message-convention items:
- 3 internal 'persisted ...' ValueErrors are immediately re-raised by
  the conforming 'Training [%s]: cannot continue ...' DependencyException
  wrapper; prefixing them would double-scope the surfaced text.
- FileExistsError(path) carries no literal message.

Line-count neutral: BasedPyright ReforceXY snapshot unaffected.