Figure out Docker problem with phpmyadmin service

[juhanikat]

See #1177

[karilint]

I looked into the phpMyAdmin setup without changing code.

Findings:

• docker-compose.dev.yml and docker-compose.anon.yml both define a phpmyadmin service using phpmyadmin:5.2.1.
• Both publish the same fixed host ports: 8080:80 and 9090:443.
• The compose files parse correctly with docker compose -f docker-compose.dev.yml config --services and docker compose -f docker-compose.anon.yml config --services.
• I do not see an obvious phpMyAdmin configuration problem that would require removing the service entirely.

Most likely causes if it fails only on some machines:

• Port 8080 or 9090 is already used by another local process/container.
• A stale/orphan compose container exists from switching between docker-compose.dev.yml and docker-compose.anon.yml. Both stacks use the same service name (phpmyadmin) from the same project directory, so Docker Compose may try to reuse/attach to an old container.
• Running the dev and anon stacks at the same time will also conflict on the phpMyAdmin ports.

Suggested local checks:

• docker ps -a --filter name=phpmyadmin
• docker compose -f docker-compose.dev.yml ps
• docker compose -f docker-compose.anon.yml ps
• Check whether ports are occupied, e.g. lsof -i :8080 / lsof -i :9090 on macOS/Linux, or the equivalent Windows command.

Safe cleanup options before retrying:

• Stop the stale phpMyAdmin container: docker stop nowdatabase_react-phpmyadmin-1 if that exact container exists.
• Or stop the service via the matching compose file: docker compose -f docker-compose.dev.yml stop phpmyadmin or docker compose -f docker-compose.anon.yml stop phpmyadmin.

I would not merge a change that removes phpMyAdmin yet if it works on other laptops. This may be enough as documentation/troubleshooting unless someone can reproduce a phpMyAdmin-specific error after confirming the ports and stale containers are clean.