Fix location fetch: use numeric LocationRefreshMode enum (Google API change)

[miditt]

Problem

Google's kidsmanagement location endpoint no longer accepts the string values "REFRESH" / "DO_NOT_REFRESH" for locationRefreshMode. Requests now fail with:

HTTP 400: Invalid value at 'location_refresh_mode'
(type.googleapis.com/google.kidsmanagement.v1.LocationRefreshMode), "REFRESH"

Because async_get_location returns None on a non-200 response, the device_tracker silently freezes on the last position that succeeded before Google's change — no error surfaced to the user, just a stale location.

Fix

Google now requires the numeric enum values. Switched to 2 (REFRESH) / 1 (DO_NOT_REFRESH), both verified returning HTTP 200 against the live API. Added named class constants with an explanatory comment.

Testing

Reproduced the 400 with the string value and confirmed 200 + a fresh GPS fix with the numeric value, against a live supervised account. Deployed to a running HA instance; device_tracker location resumed updating immediately.

[noiwid]

Thanks a lot for this @miditt - excellent diagnosis and a very clean fix. 🙏

Confirmed on my side: Google's kidsmanagement location endpoint now rejects the string LocationRefreshMode values and only accepts the numeric enum. The failure mode was exactly as you described - async_get_location returns None on the 400, so the device_tracker silently froze on the last known position with nothing surfaced to the user. Nasty one to catch.

Merged into main. I only dropped the manual manifest.json version bump (1.2.11) from the branch, since the version is bumped automatically by the release workflow when I cut a GitHub Release - the API fix itself went in untouched. This will ship in the next release. Thanks again for testing it against the live API and reporting the before/after so clearly! 🚀