* use composer version of geoip library

* region london was renamend in latest geoip version

* Handle actions with title only correctly

* use action with empty url for tests

* update expected ui files

* Issue the CORS header (Access-Control-Allow-Origin) also on Tracking API requests

* Move CORS code to the Tracking API endpoint file

* Adds a note about cross domain linking requiring multiple domains. Adds a new i18n key CoreAdminHome_JSTracking_CrossDomain_NeedsMultipleDomains

* Update en.json

* Make all new segments "Pre-processed" when browser_archiving_disabled_enforce=1

If real time processing of segments is disabled via browser_archiving_disabled_enforce=1
then any segment set to "segmented reports are processed in real time (default)"
will NEVER be showing data (except in the Live/real time reports)

With this PR all new segments will be set to "segmented reports are pre-processed (requires cron)"

It does not fix up existing real segments, but existing real time segments would display a modal explaining the issue (refs https://github.com/piwik/piwik/issues/12253)

* Re-use existing method

* Re-use existing method

* Introduce config setting to show update notifications to superusers only. Fixes #7930

* By default, all users should see the update notification

* Changed description of config param

* Updates changelog

* make HTML in safemode-page valid

* update UI test

Otherwise the topbar will be always hidden as there is no text for it. Only affects demo.piwik.org

To make sure as many tracking requests will be tracked as possible eg on "unload" of the page. Did not test it specifically but shouldn't cause any trouble.

Add visitor details events

Similar to Report.add/filterReports, Widget.add/filterWidgets, etc

We can change naming but kept it consistent with these existing events. It may be a bit confusing to have `Live.addVisitorDetails` and `Live.filterVisitorDetails` vs `Live.getAllVisitorDetails`. For `Live.getAllVisitorDetails` you would then expect it returns maybe all visitor detail instances. The first 2 work basically on the raw instances, whereas `Live.getAllVisitorDetails` works on the actual visitor details data. Any thoughts @sgiehl ?

added $_COOKIE to RequestSet environment

changes to dashboard weren't saved anymore when changing series selection

* Ensure segment param is always considered for widget urls

* Adds ui test for segmented dashboard

* Do not show bundles in premium feature widgets

* filter bundles in widget itself and not in template

* Make it possible to change the number af maximum visits aggregated for visitor profile

* update expected screenshot

Fix addTracker does not return the tracker instance

* Formats numbers in the real time widget

* Defers real-time widget formatting to the view only