v1.10.0 — pull from production by default, whatever it is called

With no environment given and none pinned, ddev upsun-db-pull, ddev upsun-files-pull and ddev pull platform|upsun now pull from the project's production environment. Upsun reports it via project:info default_branch.

Newer sites deploy production from main, not master (OP-946), and across the fleet production branches also include rangefinder and trendlabs. So nothing is guessed; the project is asked.

This replaces DDEV's stock fallback, the local git branch. From a feature branch or a worktree, that targeted an environment that usually doesn't exist, and resumed it when it did and was Inactive.

Precedence: explicit argument → PLATFORM_ENVIRONMENT pinned in .ddev/config.yaml → production.

Upgrading: two steps, both needed

1. The provider recipes are not replaced automatically. They omit #ddev-generated on purpose, so ddev add-on get skips them on an existing repo. Delete them first:

rm .ddev/providers/platform.yaml .ddev/providers/upsun.yaml
ddev add-on get Rapid-Development-Group/ddev-rdg

2. Consider dropping your PLATFORM_ENVIRONMENT pin. If .ddev/config.yaml pins PLATFORM_ENVIRONMENT=master and production is master, the pin is now redundant, and it's the thing that breaks the day the project moves to main. Keep a pin only if the repo should pull from something other than production by default.

229 tests, up from 227.

Full changelog: v1.9.0...v1.10.0