Telemetry for official plugins

[Rafikooo]

Alternative approach to #1 — uses a compiler pass instead of a bundle, so end users don't need to touch bundles.php.

Ref: Sylius/Sylius#18588

Uses a compiler pass that plugins register in their build() method. When SyliusCoreExtension skips loading telemetry services (because the user disabled telemetry via ENV or config), the compiler pass loads them directly from SyliusCoreBundle.

This approach requires no action from end users — no bundles.php changes, no Flex recipe. The plugin's composer require sylius/telemetry + compiler pass registration is enough.

How it works

1. If telemetry services are already in the container → noop
2. If Sylius version predates telemetry (TelemetrySendManagerInterface doesn't exist) → noop
3. If dev/test environment → noop
4. Otherwise → loads all config files from SyliusCoreBundle/Resources/config/services/telemetry/ via DirectoryLoader (supports both XML and PHP formats)

Usage in a plugin

use Sylius\Telemetry\TelemetryCompilerPass;

final class FooPlugin extends Bundle
{
    public function build(ContainerBuilder $container): void
    {
        $container->addCompilerPass(new TelemetryCompilerPass());
    }
}