chore: even name update

[Shahroz16]

Note

Medium Risk
Changing the emitted track event name is potentially breaking for customers relying on the previous "Location Update" name in journeys/segments and analytics dashboards. No functional logic changes beyond the renamed event string and related docs/comments.

Overview
Updates EventNames.LOCATION_UPDATE from "Location Update" to "CIO Location Update", which changes the name used for the location module’s track events.

Aligns location module documentation/comments (LocationTracker, ModuleLocation) to reference the new event name.

^{Written by Cursor Bugbot for commit 9db40e3. This will update automatically on new commits. Configure here.}

[github-actions]

Sample app builds 📱

Below you will find the list of the latest versions of the sample apps. It's recommended to always download the latest builds of the sample apps to accurately test the pull request.

---

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.00%. Comparing base (88b1971) to head (9db40e3).
⚠️ Report is 1 commits behind head on feat/real-time-location.

Additional details and impacted files

@@                    Coverage Diff                     @@
##             feat/real-time-location     #667   +/-   ##
==========================================================
  Coverage                      68.00%   68.00%           
  Complexity                       842      842           
==========================================================
  Files                            153      153           
  Lines                           4679     4679           
  Branches                         637      637           
==========================================================
  Hits                            3182     3182           
  Misses                          1259     1259           
  Partials                         238      238           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Build available to test
Version: update-location-event-name-SNAPSHOT
Repository: https://central.sonatype.com/repository/maven-snapshots/

[github-actions]

• java_layout: update-location-event-name (1772827816)

[github-actions]

📏 SDK Binary Size Comparison Report

Module	Last Recorded Size	Current Size	Change in Size
core	31.29 KB	31.27 KB	⬇️ -0.02KB
datapipelines	40.57 KB	40.57 KB	✅ No Change
messagingpush	30.25 KB	30.25 KB	✅ No Change
messaginginapp	121.84 KB	121.84 KB	✅ No Change
tracking-migration	22.89 KB	22.89 KB	✅ No Change

[github-actions]

• kotlin_compose: update-location-event-name (1772827802)

[mrehan27]

Are tests using the same constants? Shouldn't tests refer to hardcoded values or different constants so they don't rely on same source and can catch if the name is changed unintentionally?