Enterprise license validation sometimes uses outdated token from disk instead of DB

### What happened? After reviewing the Grafana logs, we noticed that license validation periodically loads an expired token from disk instead of the current one stored in the database. This results in temporary warnings about an expired license, even though the license is valid and automatically renewed. This issue frequently occurs during infrastructure failover to a different site/location, which suggests that after service restart or relocation Grafana may read the license token from disk instead of the updated one stored in the database. Example log excerpt: _logger=licensing t=2025-11-26T07:04:58.098149778+01:00 level=info msg="Validated license token" appURL=https://xxxxxx/ source=disk status=Expired logger=licensing.renewal t=2025-11-26T07:04:58.098181025+01:00 level=warn msg="failed to load or validate token" err="license token expired at 2025-09-09 10:03:26 +0000 UTC" logger=licensing t=2025-11-26T08:04:58.110717378+01:00 level=info msg="Validated license token" appURL=https://xxxxxxx/ source=db status=Valid_ Grafana checks the license every hour and normally reads the updated token from the database. However, occasionally it retrieves the token from disk, where the value is outdated. This causes false expiration warnings until the next validation run. The license was activated by placing the license file on disk. My config: _license_path = /etc/grafana/license.jwt auto_refresh_license=true_ ### What did you expect to happen? Grafana should always prioritize the newest token stored in the database for validation. Additionally, Grafana should update/overwrite the token stored on disk when the license is renewed, preventing outdated tokens from being used at all. ### Did this work before? It didn't work. ### How do we reproduce it? 1. Install and activate Grafana with a license that renews automatically. 2. Observe licensing logs over time. 3. Occasionally, validation uses the token from disk despite a valid one being stored in DB. ### Is the bug inside a das…