turbo:visit is dispatched twice on redirect

[domchristie]

With the following flow:

1. User clicks link to /one
2. turbo:visit is fired
3. /one redirects to /two
4. turbo:visit is fired again

There's currently no way to accurately determine whether a Visit was triggered by a click, a redirect, or programmatically via Turbo.visit. This is useful for animating page transitions: an animation library could animate on the first turbo:visit, and ignore the redirect visit.

Perhaps it'd be worth detailing the reason in event.details, similar to the reload event?

[morki]

This also causes problems with buitin progressbar, which is jumping wierdly on redirect.