Enable secure sudo access for GitLab Remote Development workspaces

What this post added

This post introduces the capability to enable secure sudo access for GitLab Remote Development workspaces. It details the challenge of needing elevated privileges within workspaces for tasks like package installation and debugging, and how this is prevented by default due to security measures. The post then explains three methods to enable this secure sudo access: Sysbox, Kata Containers, and user namespaces, providing Kubernetes and GitLab agent configuration details for each. It concludes with a demonstration of creating a workspace with these configurations and successfully installing and using `jq` for log analysis.