ci: run composer commands with sudo in plugin CI workflow

[TheWitness]

Summary

The Install Composer Dependencies step in .github/workflows/plugin-ci-workflow.yml ran composer config, composer require, rm, and composer install without sudo. Recent changes to the CI runner mean these commands need elevated permissions to write to the shared cacti checkout, so the step was failing.

Changes

• Prefix composer config, composer require, rm -f composer.lock, and composer install with sudo in the Pest install step.
• Drop the deprecated --dev flag from composer require (Composer no longer supports it on require).

Before

composer config --no-plugins allow-plugins.pestphp/pest-plugin true
composer require --dev --no-progress --no-interaction "pestphp/pest: ^3" "pestphp/pest-plugin-drift: ^3.0"
rm -f composer.lock
composer install --dev --no-progress

After

sudo composer config --no-plugins allow-plugins.pestphp/pest-plugin true
sudo composer require --no-progress --no-interaction "pestphp/pest: ^3" "pestphp/pest-plugin-drift: ^3.0"
sudo rm -f composer.lock
sudo composer install --dev --no-progress

[Copilot]

🟡 Changes recommended

Composer plugin execution and production-versus-development dependency handling need correction.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

This pull request updates the plugin CI workflow to run Composer operations with elevated permissions and adjusts Pest dependency installation.

Changes:

• Adds sudo to Composer and lockfile commands.
• Removes the deprecated --dev flag from composer require.

File summaries

File	Description
.github/workflows/plugin-ci-workflow.yml	Adjusts Composer dependency installation in CI.

Review details

Suppressed comments (1)

.github/workflows/plugin-ci-workflow.yml:134

• Removing --dev changes Composer's target section: composer require will add these test-only packages to require, while the later composer install --dev only controls what is installed and does not move them back to require-dev. Keep the dev flag (or use the supported equivalent) so the CI-only Pest dependencies are not recorded as production requirements.

          sudo composer require --no-progress --no-interaction "pestphp/pest: ^3" "pestphp/pest-plugin-drift: ^3.0"

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[bmfmancini]

LGTM - thanks @TheWitness.