feat(plugin): align with Shopware plugin guidelines

- add dedicated monolog channel aeon_dump_manager and log dump jobs
- migrate services.xml/routes.php to YAML
- require PHP ^8.2
- add extension icon and .config/shopware-extension.yml
- drop empty lifecycle overrides

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

CLAUDE.md

@@ -14,7 +14,7 @@ the full build spec live under `.scratch/admin-dump-manager/` and `.scratch/dump
 - Plugin bootstrap class: `src/AeonDumpManager.php` (extends `Shopware\Core\Framework\Plugin`) — this
   is the entry point Shopware calls for install/uninstall/activate/deactivate/update lifecycle hooks.
 - Plugin class name is wired via `composer.json` → `extra.shopware-plugin-class`.
-- Services are registered manually in `src/Resources/config/services.xml` (Symfony DI, XML format,
+- Services are registered manually in `src/Resources/config/services.yaml` (Symfony DI, YAML format,
   autowiring is not configured — every new service/command/task must be added here explicitly with
   its tag, e.g. `console.command` or `shopware.scheduled.task`).
 - Plugin store-config UI fields (e.g. `maxDumps`, `retantionDays`) are defined in
@@ -66,7 +66,7 @@ vendor/bin/phpunit tests/SomeTest.php            # single file
 ## Adding functionality
 
 - New console commands go in `src/Command/`, new scheduled tasks in `src/ScheduledTask/` — both must
-  be registered in `src/Resources/config/services.xml` with the appropriate tag or Shopware will not
+  be registered in `src/Resources/config/services.yaml` with the appropriate tag or Shopware will not
   discover them.
 - Scheduled tasks need a matching handler (tagged `messenger.message_handler`) to actually run; a bare
   `ScheduledTask` subclass like `ExampleTask` only defines the schedule, not the behavior.