Research ESPHome EcoNet local control for Rheem

## Summary
Research `esphome-econet` as a local-control alternative or complement for the Rheem EcoNet water heater path.

This was split out from the temporary Rheem EcoNet certificate workaround tracked in #1820 so that the cloud-certificate workaround and the local-control project can be followed separately.

## Why this is useful
`esphome-econet` is a local-control ESPHome package for Rheem appliances. It works without internet access through the appliance diagnostics port and can coexist with the cloud EcoNet integration.

This may be a practical future project if the Rheem/ClearBlade cloud path remains brittle, or if a more local control surface is preferred.

## References
- https://github.com/esphome-econet/esphome-econet
- https://github.com/home-assistant/core/issues/172228
- Parent workaround context: #1820
- Original split-out comment: https://github.com/CCOSTAN/Home-AssistantConfig/issues/1820#issuecomment-4880366165

## Research checklist
- Confirm supported Rheem model/generation and diagnostics-port requirements.
- Identify hardware needed: ESP32/ESP8266 board, wiring, connector, enclosure, and safe mounting approach.
- Review whether it exposes all currently used HA entities or better equivalents.
- Determine coexistence behavior with the current cloud EcoNet integration.
- Decide whether this belongs as a repo package, ESPHome external project, or documentation-only future project.
- If adopted, document rollback and ensure current Powerwall/Rheem automations keep working or are migrated intentionally.

Start by reviewing the linked esphome-econet project and the Rheem-related context in #1820 and #172228. Confirm model and diagnostics-port support, hardware and mounting requirements, entity coverage, cloud coexistence, project placement, and rollback implications. Done means a documented adoption decision that preserves or intentionally migrates the current Powerwall/Rheem automations.

Written by the indexing model from the issue text.