[Affects Developers only, not customers!] Pass environment variables to Preview/Production is broken

The problem is, if I try to deploy a dangerous migration passing the env variable `SAFETY_ASSURED=1`, either doing `bin/remote system preview01 db:enable_dangerous_tasks deploy branch=foo` (for this, which worked well at the time) or by `bin/remote system preview01 deploy branch=preview-blocking-migrations-and-dashboard-service-navigations SAFETY_ASSURED=1`, I see the error of the logs that I attached.

This happens at least in Preview. Not sure about Production.
Probably it isn't worth fixing it before we get the new infrastructure in Production because we can bypass this issue by doing ugly stuff (like ssh to the machine and add the ENV variable there, or in the case of migrations adding a safety_assured inside the migration itself).