This PR defines a new segment ActionType. This is especially useful when for example viewing a CustomDimensions report in scope Action. By default custom dimensions are tracked across all actions. By using eg a segment actionType=pageviews one can see all custom dimensions tracked for pageviews. Or maybe someone wants to see all Custom Dimension values for downloads and outlinks etc.

In order to make this work we had to change how event urls are tracked as the segment works on the SQL segment log_action.type. So far, when an event was tracked, we looked for a URL having the type 1 (Pageview) in log_action. To be actually able to segment for events we are now using type 10 in log_action when request was an event. Downside is we create many more entries in log_action for each URL used in an event tracking call. On the good side we now have more accurate statistics in Transition reports where exit rate and referrer are calculated more correctly since they did not differentiate between events and a pageview.

We also identified at some point it might be useful to completely remove the type column from log_action table and instead store the type of the action in log_link_visit_action. This would help to avoid creating many duplicated entries in log_action.

Re failing tests:

• There is a failing test in CustomDimensions plugin. We need to fix that test once we actually merged it. Otherwise we'd have to fix this test in a branch in CustomDimension and later change the submodule back to master in CustomDimensions once this PR is merged
• Some UI tests fail because the order of Segments failed. This is expected for now and not a problem