Chore: Add anonymous user ID in tracking events

[aaronsteers]

Resolves: https://github.com/airbytehq/airbyte-internal-issues/issues/6482

This is ready for review.

1. On first run, PyAirbyte will check for an existing analytics file.
2. If not found, and if DO_NOT_TRACK is not set, a new ID will be generated and will be stored in a yaml file at ~/.airbyte/analytics.yml
3. If AIRBYTE_ANALYTICS_ID env var is set, then the provided ID will be used instead of a randomly generated one. In this case, the provided analytics ID will also be saved to the analytics file, overriding any previously set value.
4. This PR updates all of our CI jobs to pass in a (newly created) repository variable (here), which contains a newly generated ULID that is specific to our CI flows.

[aaronsteers]

After running PyAirbyte locally, I now have the file as expected:

AJ-Steers-MacBook-Pro---GGHWM7QWPJ:.airbyte ajsteers$ pwd
/Users/ajsteers/.airbyte
AJ-Steers-MacBook-Pro---GGHWM7QWPJ:.airbyte ajsteers$ cat analytics.yml
# This file is used by PyAirbyte to track anonymous usage statistics.
# For more information or to opt out, please see
# - https://docs.airbyte.io/pyairbyte/anonymized-usage-statistics
anonymous_user_id: 01HRT5XN7NPS12DWZX5RTXHAE8

We write the file as plain text but it is intended to be parsed as yaml. The reason for writing as plain text is that this allows us to more easily control formatting and the header comment text.

I realize we still need to have a real URL to point people to. The one above is not a real page as of yet.

[bindipankhudi]

Looks great! :) One minor comment, non-blocking.