feat!: Adds telemetry client calls to worker

[marofke]

Note: Depends on aws-deadline/deadline-cloud#60

What was the problem/requirement? (What/Why)

We want to gain insights into how our customers use our software.

What was the solution? (How)

Use the Telemetry Client introduced in the Deadline Cloud Client Library, since it's a requirement for the Worker Agent already. We introduce an installer option to opt out of telemetry collection if customers choose, which calls the client lib to set the config setting.

What is the impact of this change?

We can now collect simple startup data on Worker machines, so we know what kinds of machines typically get used for worker flows.

Further, the worker installer bash script was updated a bit to refactor the bin directory we search for installed programs, since we need to call the Deadline client lib to set the telemetry opt out option.

How was this change tested?

• included the changes from feat!: Adds more telemetry events deadline-cloud#60
• built locally, and confirmed telemetry events were sent to our backend, and ensured none were sent through unit tests
• installed all the packages on a fresh linux EC2 instance, and confirmed that telemetry opt out works as an installer option

[ec2-user@ip-172-31-20-107 ~]$ python -m venv /tmp/tmp-env
[ec2-user@ip-172-31-20-107 ~]$ source /tmp/tmp-env/bin/activate
(tmp-env) [ec2-user@ip-172-31-20-107 ~]$ pip install openjd_model-0.1.1-py3-none-any.whl openjd_sessions-0.2.0-py3-none-any.whl deadline-0.28.0.post1+g3f40b9e-py3-none-any.whl deadline_cloud_worker_agent-0.14.1.post4+gcb4fe9f.d20230926-py3-none-any.whl
(tmp-env) [ec2-user@ip-172-31-20-107 ~]$ install-deadline-worker --farm-id $FARM --fleet-id $FLEET --telemetry-opt-out --no-install-service
===========================================================
|      Amazon Deadline Cloud Worker Agent Installer       |
===========================================================

Farm ID: farm-56bc3eb734a24cbf871985aa2221597f
Fleet ID: fleet-3e9ba17545f040cc8d83502b82251242
Region: us-west-2
Worker agent user: deadline-worker-agent
Worker job group: deadline-job-users
Scripts path: /tmp/tmp-env/bin
Worker agent program path: /tmp/tmp-env/bin/deadline-worker-agent
Worker agent program path: /tmp/tmp-env/bin/deadline
Allow worker agent shutdown: no
Start systemd service: no
Telemetry opt-out: yes
Confirm install with the above settings (y/n):y

Worker agent user deadline-worker-agent already exists
Job group deadline-job-users already exists
Worker agent user (deadline-worker-agent) is alread in job group (deadline-job-users)
No prior sudoers shutdown rule at /etc/sudoers.d/deadline-worker-shutdown
Provisioning log directory (/var/log/amazon/deadline)
Done provisioning log directory (/var/log/amazon/deadline)
Provisioning persistence directory (/var/lib/deadline)
Done provisioning persistence directory (/var/lib/deadline)
Provisioning configuration directory (/etc/amazon/deadline)
Done provisioning configuration directory
Configuring farm and fleet
Done configuring farm and fleet
Opting out of telemetry collection
Done
(tmp-env) [ec2-user@ip-172-31-20-107 ~]$ sudo cat /home/deadline-worker-agent/.deadline/config
[telemetry]
opt_out = true

Was this change documented?

N/A

Is this a breaking change?

Yes, since the installer script interface changed

[crowecawcaw]

Where do we only send telemetry when its configured to be one? I might be missing something obvious. Is opt-in/out handled in another component?