Don't send timeline events to analytics

These are effectively audit logs and therefore we don't need to send
them to BigQuery as we already have a record of when data changed in the
analytics itself.

config/analytics.yml

@@ -358,34 +358,6 @@
     - trn
     - updated_at
     - uuid
-  :timeline_events:
-    - age_range_max
-    - age_range_min
-    - age_range_note
-    - application_form_id
-    - assessment_id
-    - assessment_section_id
-    - assignee_id
-    - column_name
-    - created_at
-    - creator_id
-    - creator_name
-    - creator_type
-    - event_type
-    - id
-    - mailer_action_name
-    - mailer_class_name
-    - message_subject
-    - new_value
-    - note_id
-    - old_value
-    - qualification_id
-    - requestable_id
-    - requestable_type
-    - subjects
-    - subjects_note
-    - updated_at
-    - work_history_id
   :uploads:
     - created_at
     - document_id

config/analytics_blocklist.yml

@@ -44,4 +44,31 @@
   :teachers:
     - access_your_teaching_qualifications_url
   :timeline_events:
+    - age_range_max
+    - age_range_min
+    - age_range_note
+    - application_form_id
+    - assessment_id
+    - assessment_section_id
+    - assignee_id
+    - column_name
+    - created_at
+    - creator_id
+    - creator_name
+    - creator_type
+    - event_type
+    - id
+    - mailer_action_name
+    - mailer_class_name
+    - message_subject
+    - new_value
+    - note_id
     - note_text
+    - old_value
+    - qualification_id
+    - requestable_id
+    - requestable_type
+    - subjects
+    - subjects_note
+    - updated_at
+    - work_history_id

config/analytics_pii.yml

@@ -53,11 +53,6 @@
     - email
     - last_sign_in_ip
     - unconfirmed_email
-  :timeline_events:
-    - age_range_note
-    - new_value
-    - old_value
-    - subjects_note
   :work_histories:
     - canonical_contact_email
     - city