chore: release as 0.0.6; compare the version check against published releases

- composer.json 0.0.6, CHANGELOG entries of the withdrawn 0.1.0/0.1.1 merged into [0.0.6]
- version-changelog: version must exceed the latest published release (main may carry a
  version whose release was withdrawn), instead of exceeding main's version

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

CLAUDE.md

@@ -77,8 +77,9 @@ Gitea workflows in `.gitea/`, plugin-agnostic (name/version come from `composer.
 runs from its official Docker image, intentionally unpinned (`latest`): a red build after a CLI release
 means fix the config.
 
-- `workflows/plugin-checks.yml` (PRs into `main`) has three jobs: `version-changelog` (every PR into
-  `main` must bump `composer.json` version and add a matching `## [x.y.z]` CHANGELOG heading), `package`
+- `workflows/plugin-checks.yml` (PRs into `main`) has three jobs: `version-changelog` (the
+  `composer.json` version must be greater than the latest published Gitea release and have a matching
+  `## [x.y.z]` CHANGELOG heading), `package`
   (shared composite action `actions/package`: `shopware-cli extension package`, `extension validate` on
   the zip, `scripts/ci/assert-built-assets.sh`), and `phpunit`. The package job caches the tested zip
   keyed by the commit's tree hash.