Simplify static or DHCP address kind configuration for templated commercial devices

**Describe the problem you have/What new integration you would like**

I have a Tubes Zigbee Coordinator, it runs ESPHome, and it publishes a `package_import_url`.
All is good, I can discover it in ESPHome dashboard, and I can update it.
What I can not easily do is change the IP address configuration from DHCP to static.
I had to copy the yaml, change the ethernet component to static configuration, and then use use_address to to update.

Problem is that I now need to keep track of any upstream updates, and then apply them to my yaml file.

I am requesting a mechanism where a manufacturer can keep their yaml up to date, but I can change my deployment of their device, be it WiFi or Ethernet, and I can define DHCP or static IP/gateway/subnet/DNS.
E.g. in the ESPHome dashboard, select the device, and change network configuration, having the dashboard change templated values, and update using the old IP, switching to the new IP when done.

**Please describe your use case for this integration and alternatives you've tried:**

Today I copy the yaml and make local edits that can get out of sync with the vendor's file.

**Additional context**

https://github.com/tube0013/tube_gateways/blob/main/models/current/tubeszb-cc2652-eth_usb/firmware/esphome/tubezb-cc2652p2-ethusb-2022.yaml
@tube0013