Show and sort by device local IP in dashboard

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

When registering a new esphome device, I would like to quickly out find what is the highest static ip number already registered so cascading disconnects won't likely happen. Like the title suggests, it would help if the dashboard would present device ip, would be ale to sort by ip and better yet, it should give an **squiggly red line when trying to use an already reserved esphome ip in yaml**.

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

I'm having a constantly increasing number of esphome devices on my home lan. On my not so realible wifi, ip conflicts will occur especially when a device with static IP is not connected and DHCP server gives a temporary lease.
Yes i'm not handling this correctly, I'm not a network guy and i feel like i need to be one when fixing means reserving desired ip in dhcp server for problematic esphome (usually with low number), editing out reserved ip in yaml (it's needed, wont ota with new ip directly, not sure if it's a feature or a bug), compile and ota while ensuring the other thing that occupies current ip is powered down, reserve new ip in yaml, ota again, copy all entity names in Home Assistant that are now unavailable, delete device in HA, add it back with new ip, name entities ids back again in HA for automations and templates to work.

**Additional context**

A workaround is creating a home assistant card with ip list (esphome text sensor entities) but it's not automatically updating for new esphome devices. I'm aware that presenting too manythings in the dashboard can overwhelm new users so maybe not enable it by default, it could simply be set in the addon config.

Start from the dashboard and the ESPHome YAML static-IP configuration described in the issue; the payload names no files or tests. Define the scope for displaying and sorting device local IPs and warning about duplicate reserved addresses, then identify how those values are represented before estimating implementation and validation work.

Written by the indexing model from the issue text.