Remove CONTROLLER_DEVELOPMENT_MODE in favor of specific settings

[mflendrich]

Problem Statement

Using a one-size-fits-all dev mode approach violates one of the 12-factor principles https://12factor.net/dev-prod-parity and we're seeing it cause real-world problems.

Proposed Solution

1. Get rid of the CONTROLLER_DEVELOPMENT_MODE setting in favor of specific settings for specific behaviors.
2. Determine the minimal set of those "specific behaviors" that must be different on CI than in production and only enable those.

Additional Information

I speculate that allowing non-allowlisted image tags could move from a runtime knob to e.g. an annotation (or some other kind of config as code parameter).

Acceptance Criteria

• CONTROLLER_DEVELOPMENT_MODE does not exist anymore
• CI has anonymous reports disabled and everything else in dev mode enabled unless there's a well understood reason for that particular bit to be non-default