Reintroduce adding timestamp to GitLab Standard Context
What does this MR do and why?
Related to https://gitlab.com/gitlab-org/gitlab/-/issues/345036.
This reintroduces !75418 (merged), which was previously reverted in !77232 (merged) due to inconsistent timestamp formats for Snowplow frontend and backend events, which tripped up the GitLab Standard Context schema (#349109 (closed)).
The changes should now be working fine due to corrective actions, which relaxed the schema that validated the timestamps. This is acknowledged in #349109 (comment 793507851) and https://gitlab.com/gitlab-org/gitlab/-/issues/345036#note_801729803.
Nevertheless, we should manually double-check if both frontend and backend events work correctly in Snowplow Micro with these changes before merging.
Screenshots or screen recordings
Got a bunch of good backend and frontend events:
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.