Update development environment to Docker Compose v2 and WordPress latest specs

[Copilot]

Docker Compose v1 (docker-compose) is deprecated and the environment used outdated image references and startup ordering patterns.

docker-compose.yml

• Removed top-level version: '3' field (obsolete in Compose v2)
• mariadb:latest → mariadb:lts; added healthcheck so dependents wait for DB readiness
• depends_on upgraded to condition: service_healthy / service_started across all services
• phpmyadmin/phpmyadmin → official phpmyadmin image; removed deprecated links: in favour of PMA_HOST: db
• Added WORDPRESS_DB_NAME: wordpress to wordpress and wordpress-cli services

CLI / tooling

• .gitpod.yml: docker-compose → docker compose (Compose v2 plugin)
• docker-instructions/README.md: all command examples updated to docker compose

WordPress defaults

• settings.sh / settings-sample.sh: default theme twentynineteen → twentytwentyfive

Original prompt

Update the Development Environment to the latest specs of docker and Wordpress

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[zoukkinen]

Make sure that the scripts in the docker-instructions folder are valid bit these changes

[Copilot]

Make sure that the scripts in the docker-instructions folder are valid bit these changes

Found and fixed two bugs in the scripts (commit 0759689):

• apache2-wp-cli.sh (line 142): Removed a stray § character before echo "" inside the DO_SEARCH_REPLACE block — this would have caused a "command not found" shell error whenever search-replace was enabled.
• wp-cli-multidomain.sh (line 2): Fixed set x → set -x — without the -, bash was setting the positional parameter $1 to "x" instead of enabling debug tracing.

Both scripts now pass bash -n syntax validation. The theme change to twentytwentyfive in settings.sh/settings-sample.sh is also valid — it's the default bundled theme in current WordPress.