sudo does not work with 2026 containers

[jfpanisset]

In 2024 / 2025 images based on gcc-toolset 11, sudo is a shell script wrapper in /opt/rh/gcc-toolset-11/root/usr/bin/sudo which preserves PATH and LD_LIBRARY_PATH whereas in 2026 images based on gcc-toolset 14, no such wrapper is provided, and thus the sudo command will only look in the directories defined by secure_path in /etc/sudoers and will not preserve LD_LIBRARY_PATH:

Defaults    secure_path = /sbin:/bin:/usr/sbin:/usr/bin

So a command like:

sudo pip3 install foo

expecting to pick up /usr/local/bin/pip3 will not work, and trying to fully specify:

sudo /usr/local/bin/pip3 install foo

won't work either since pip3 / python3 won't find its DSOs in /usr/local/lib

This project only uses sudo once (being removed) and thus doesn't require sudo to work.

For now we remove the spurious use of sudo in ci-usd/image.yaml, but we should decide if we want to restore sudo behavior to match 2024 / 2025 images for any external users who may need to run script depending on a working sudo.