Capture window.location.href during capture phase of UI event

[schwartzmx]

If we don't capture this as early as possible then there is a chance the action caused a location change and once ultimately logged will have the URI for where the action took the user and not necessarily where the action took place.

Example, click anything that causes a page transition. If this lookup is delayed it will get the destination URI and not where the action took place.

Open to naming this something else, but windowLocationHref seemed a bit excessive, uri or page_uri may work so long as it's clear where it comes from.