Welcome Tour / WPCOM Tours: Update Tracks events to handle multiple tour specs

[chriskmnds]

Details

We currently record a number of registered Tracks events as users interact with the Welcome Tour. These aid in AB testing the impact of changes/functionality/content we ship in the tour. These are mostly passed along as callbacks to Tour Kit (and more in the way of that as the Wpcom Tour Kit variant is extracted). We should probably rethink and update these events to enable tracking around multiple tour specs.

"WPCOM Tours" -> candidate name of the package we intend to ship as part of Step 3 in relevant project thread: pdDR7T-5-p2

Checklist

• Get the list of events we have registered. Would be nice to P2 about them for input, ensure they are sufficient.
• Rethink/update in the context of multiple tour specs.
• Remove the is_gutenboarding flag from the events defs and stop passing it through.
• Consider introducing more props to the events to track a little better e.g. timestamp, host/URL, etc. Consider the sort of questions/analysis we intend to do with these.
• Address any other TODOs added in comments around the recordTracksEvent calls.
• Start planning out some notes for a new FG page on "WPCOM Tours".

Related

No response