Remove shownas filter and move stickiness/lifecycle into separate insight tabs

[EDsCODE]

Changes

Adhoc changes to separate stickiness and lifecycle into separate insight tabs. Logic will be reorganized if data shows better usage and we commit to making this change

Please describe.

• places this separation behind feature flag remove-shownas to test usage

If this affects the frontend, include screenshots.

Checklist

• All querysets/queries filter by Organization, by Team, and by User
• Django backend tests
• Jest frontend tests
• Cypress end-to-end tests

[paolodamico]

Great idea here! Definitely an improvement on the discoverability of these features, and is definitely more intuitive.

Almost everything is 100%, a few points after the QA:

• Found an edge case in which after switching between any trends tab and either the "Stickiness" or "Lifecycle" tab, it would no longer let you change the selected event (see recording below with the error and dropdown not changing).
• On the lifecycle view, I can remove the first event and then I'm allowed to add multiple events/actions (see below for suggestion on UX improvement).

Some potential improvements:

• I would use this opportunity to reorder the insights a bit, doing Trends & Funnels first (most used), and adding these two new spin-offs to the end (that way I believe it's even more clear that you now can do that stuff).
• I would consider adding a "NEW" badge to the lifecycle insights to increase discoverability for this new feature. The badge should only appear until you use this for the first time.
• As you hide the math selector for the lifecycle view, maybe we should keep the select box disabled showing "Unique users"? Thinking that could make it even clearer.
  • Related to the above I would remove the "Add graph series" button altogether in the lifecycle graph. I would also not allow the user to remove the one (only) event/action.

P.S. Great stuff A/B testing this! Will merge #2787 soon to be able to measure the results accurately.

[EDsCODE]

@paolodamico ready for another look. I did everything except the new badge and locking the math selector on lifecycle. The new badge is cool but I think it's better in a follow up PR so if we want it, we can hold off an initiating feature flag for this until i finish the new badge. I don't think we should leave in a disabled math selector because I tried it and it just looks more confusing why you can't select other options. I'd suggest we work on making the description for lifecycle abundantly clear

[paolodamico]

lgtm! everything seems addressed!