Fix workflow failure: remove --no-plugins flag from composer install in reports and wiki workflows

[coisa]

Problem

PR #35 introduced a regression that breaks the reports and wiki workflows. The --no-plugins flag was added to the composer install command, preventing the dev-tools Composer plugin from being activated.

Current Behavior

The composer install command in .github/workflows/reports.yml and .github/workflows/wiki.yml runs with --no-plugins, causing the dev-tools plugin to not be available when running subsequent dev-tools commands (e.g., dev-tools reports, dev-tools wiki).

Expected Behavior

The composer install should allow plugins to be installed so that dev-tools can function properly.

Failure Surface

• .github/workflows/reports.yml line 41
• .github/workflows/wiki.yml line 46

Proposal

Remove the --no-plugins flag from the args in both workflow files while keeping the other improvements from PR #35 (fixed cache path, composer.lock hash, etc.).

Implementation Strategy

1. In .github/workflows/reports.yml: Change args from --prefer-dist --no-progress --no-interaction --no-plugins --no-scripts to --prefer-dist --no-progress --no-interaction --no-scripts
2. In .github/workflows/wiki.yml: Same change

Non-goals

• Do not revert the other improvements (cache path, composer.lock hash, explicit command/args)

Acceptance Criteria

Functional Criteria

• --no-plugins flag removed from reports.yml
• --no-plugins flag removed from wiki.yml
• Workflows run successfully without the plugin flag

Regression Criteria

• dev-tools plugin is available during workflow execution
• dev-tools reports runs successfully
• dev-tools wiki runs successfully

Closes #35