Global workflows should not require per-project plugin installation

[alquerci]

Version: 0.11.0
Os: linux

Currently, when using a global workflow that depends on a plugin, the plugin must still be installed individually in each project where the workflow is executed.

This creates unnecessary duplication and friction, especially for workflows intended to be shared or reused across multiple projects.

Problem

A global workflow implies portability and reuse, but requiring plugins to be installed at the project level introduces:

• Repetitive setup across repositories.
• Increased maintenance overhead.
• Inconsistency between environments if plugin versions differ.

Expected behavior

If a workflow is defined as global and depends on a plugin:

• The plugin should be resolved and loaded globally, not per project.
• The workflow should execute without requiring manual plugin installation in each repository.

Actual behavior

• The CLI requires the plugin to be explicitly installed in every project using the workflow.

Suggested solution

• Allow plugins to be installed and resolved at a global scope.
• Ensure the CLI prioritizes globally available plugins when executing global workflows.
• Optionally provide a fallback mechanism or a clear error if neither global nor local plugin is available.

Additional context

This would significantly improve the developer experience for teams using shared workflows across multiple repositories.