Feat(Teslemetry) - enable tbc control by default

[springfall2008]

Teslemetry TBC control seems to work better, getting full charge rate

Enable: teslemetry_tbc_control by default.

[springfall2008]

🤖 Automated first-pass triage (a maintainer will review before any action is taken).

Classification: enhancement — graduating the teslemetry_tbc_control trial setting (added in #4892, PR #4976) from opt-in to default-on.

Scope of the change (confirmed against current main, v9.0.3-177-g8b9fe029 — no code change on main since the reporter's request):

1. The functional flip is one line: apps/predbat/components.py:635 — "tbc_control": {"required": False, "default": False, ...} → default: True. Anyone with an explicit teslemetry_tbc_control: False keeps the real-rate path; read-only users are unaffected either way (sync_tariff returns early at teslemetry.py:1412). The flip only reaches users with teslemetry_automatic: True who never set the key.
2. Template: templates/teslemetry.yaml:38 still carries the commented #teslemetry_tbc_control: True hint — should be removed once it's default.
3. Docs: docs/components.md:1110 (defaults table says false) and docs/inverter-setup.md:2975/:2980 (template block and the "off by default" paragraph) all describe it as off by default.
4. Tests: test_teslemetry_tbc_control_defaults_off_and_uses_the_real_rate_tariff (apps/predbat/tests/test_teslemetry.py:1141) pins the off-default and the real-rate tariff push, so it needs renaming/updating with the flip; test_teslemetry_initialize_sets_tbc_control_from_component_arg (~:1176) asserts the mock's class default, which is not registry-driven and should survive the flip.

What enabling it does (matching the "full charge rate" in the issue body): with the flag on, sync_tariff pushes the signal tariff (0p over the charge window / 100p over the export window / 50p import elsewhere) instead of the real-rate tariff, and evaluate_schedule delegates to evaluate_schedule_tbc (teslemetry.py:589, teslemetry.py:1409-1414) — Tesla's own Opticaster then runs the charge at full rate rather than the slower reserve-driven charge, while Predbat's charge/export target percentages become advisory.

One thing worth weighing when defaulting it on: the documented 81-99% reserve-band limitation (docs/inverter-setup.md:2980) becomes default-on behaviour — a set_reserve_min anywhere in 81-99 leaves grid charging disabled in every state, permanently, with only a one-off log line. Also possibly related: #4887 (flat ON_PEAK band on the real-rate tariff path) — defaulting to TBC would shrink that issue's blast radius to explicit opt-outs.

No additional information needed. No priority applied (feature request).