Security: Docker socket permissions in CI workflow use world-writable mode

[coderabbitai]

Issue Description

The unit test CI workflow () currently uses sudo chmod 666 /var/run/docker.sock which makes the Docker socket world-writable, creating a potential security risk even in the CI environment.

Current Behavior

The workflow grants world-writable access (0666) to the Docker socket to allow the CI runner to interact with Docker.

Security Concern

World-writable permissions on the Docker socket can be a security risk as it allows any user on the system to interact with Docker, potentially leading to privilege escalation.

Suggested Approach

Use more restrictive permissions by either:

1. Using setfacl to grant read/write access only to the current user
2. Adding the user to the docker group and using group permissions
3. Installing acl package and using Access Control Lists

Context

• Identified in PR fix: Make docker and stuff run for CI.  #3792: fix: Make docker and stuff run for CI.  #3792
• Original comment: fix: Make docker and stuff run for CI.  #3792 (comment)
• Requested by: @Flo4604

[linear]

ENG-1996 Security: Docker socket permissions in CI workflow use world-writable mode