adapter: context.env should not contain process.env

having the `process.env` variables mixed into the `context.env` object is kind of redundant and might be confusing.
`context.env` should only contain the information that is specific to the deployed environment.
an action can still use `process.env` explicitely.

Start by locating the adapter code that assembles context.env and inspect how process.env is added. Confirm the intended separation between deployed-environment data and process.env, then verify that actions can still access process.env explicitly and update or add the relevant tests if they are present.

Written by the indexing model from the issue text.