[PIWOO-806] Adopt build and distribute

[Biont]

Adopt Build & Distribute Workflow

This PR migrates the Mollie WooCommerce plugin from the deprecated build-plugin-archive.yml workflow to the new unified build-and-distribute workflow.

What changes

The new workflow replaces three previously fragmented CI/CD workflows (build-and-push-assets, build-assets-compilation, build-plugin-archive) with a single unified one. It auto-detects the project type (WordPress plugin, in our case), handles PHP-Scoper, translation downloads, asset compilation, versioning, and artifact creation — all in one place.

Branch handling — important change

The workflow introduces a dev/ prefix convention that separates source branches from distribution branches:

Development (source)	Distribution (built)
dev/main	main
dev/feature/foo	feature/foo
dev/hotfix/bar	hotfix/bar

What this means in practice:

• All active development now happens on dev/* branches
• The workflow automatically strips the dev/ prefix and pushes compiled assets to the corresponding non-prefixed branch
• The main branch will always contain production-ready built code — this is what gets tagged for releases
• PRs should be opened from dev/* branches as before, but branch protection rules and any Composer constraints referencing branch names (e.g. dev-main-built → dev-main) need to be updated

Key input renames (from build-plugin-archive)

Old	New
PLUGIN_VERSION	PACKAGE_VERSION
ARCHIVE_NAME	PACKAGE_NAME
PHP_VERSION_BUILD	PHP_VERSION
PLUGIN_MAIN_FILE	(auto-detected)
PLUGIN_FOLDER_NAME	(uses package name)