[NT-707] Naming changes and white-listing clean events

[ifbarrera]

📲 What

Updates some of the naming of certain props to reflect latest changes from insights team. Also adds white-listing on "clean" events, so that only white-listed events are sent to the data lake.

🤔 Why

More event cleanup and ensuring that only clean events go to the data lake.

♿️ Accessibility

N/A

🏎 Performance

N/A

✅ Acceptance criteria

Testing white-listing:

• Ensure that KOALA_TRACKING_ENABLED is set to true, then run the app. On app launch, you should see the event App Open track on the Koala client. You should not see it track on the data lake client.
• Navigate to a project page. You should the event Project Page Viewed track on both the Koala and Lake clients

Testing discovery props changes:

• navigate to a subcategory on discovery (ex. Ceramics). On the Explore Page Viewed event, you should see:
  • the property discover_category_name, and it should say Art (the parent category)
  • the property discover_subcategory_name and it should say Ceramics (the current category)
  • the properties discover_category_id and discover_subcategory_id
• navigate to the "Projects We Love" filter. the Explore Page Viewed event should fire with a property discover_pwl: true
• navigate to the "Saved" filter. The Explore Page Viewed event should fire with a property discover_watched: true

[ifbarrera]

This was almost completely redundant with projectProperties. Any actually unique props were moved up to the actual tracking function.

[ifbarrera]

Don't need this test anymore since we're testing white-listing events now.

[nativeksr]

	1 Warning
⚠️	Big PR

Generated by 🚫 Danger

[justinswart]

Nice - will test it further, had some minor comments for now.

[justinswart]

Nice work!