v1.2.3 — API_TOKEN authentication

Summary

Fixes the integration after EverShelf security hardening (401 Unauthorized).

Changes

• Supports EverShelf API_TOKEN (and legacy SETTINGS_TOKEN) via X-API-Token, Authorization: Bearer, and api_token query parameter
• Config flow requires the token when the server reports api_token_required
• Updated strings/translations (IT, EN, DE, FR, ES)

Upgrade notes

1. Update via HACS or copy custom_components/evershelf/
2. Reconfigure the integration with API_TOKEN from your EverShelf .env file
3. Discovery (ha_info) still works without a token; full sensors require authentication