LocationsHardware Extension v1.1

### Changed

• Reworked location ping checks to run from the visitor's browser instead of the Paymenter server.
• Updated the hardware page to read each location's ping target from the frontend and calculate latency client-side.
• Reworked the location admin field so ping_ip is now used as a ping target/endpoint field rather than a server-side IP-only field.

### Added

• Added support for secure HTTPS latency endpoints such as https://location.example.com/ping.php.
• Added support for secure WebSocket latency endpoints such as wss://location.example.com.
• Added live WebSocket ping mode with automatic reconnects and repeated measurements.
• Added frontend status handling for connection, measuring, reconnecting, unavailable, and HTTPS-required states.

### Deprecated

• Deprecated the legacy /api/locations/{location}/ping route and removed it from active route registration.
• Marked the legacy PingController as deprecated because the frontend no longer uses server-side ping execution.

### Notes

• This update is intended to display the latency of the actual visitor opening the hardware page.
• For browser-based measurements on HTTPS storefronts, ping targets must use https:// or wss://.
• If Cloudflare is used for ping subdomains, they should be set to DNS only so the measured latency reflects the location endpoint rather than Cloudflare.