Running app locally does not support other Runtime commands

**Describe the bug**
When running the app with local OW, the OW credentials are applied from the dist/.env.local file. It doesn't allow Runtime commands (e.g. `aio rt activation list`) to run automatically within the same folder. Instead, the original Runtime creds are used, so we still see the results from remote Runtime.

Workaround: go to dist/, duplicate the .env.local file to .env, update it with the same keys as original .env, using local values. Execute Runtime commands from there.

**To Reproduce**
Steps to reproduce the behavior:
1. Run the app in local mode `aio app run --local`
2. Run the action in the UI
3. Open a new terminal under the same directory, run `aio rt activation list`
4. You see the list of activation from your Runtime namespace, not the local "guest" namespace

**Expected behavior**
In local run mode, you should be seeing the local namespace results with Runtime commands executed in the same directory.

Reproduce the issue with `aio app run --local`, then run `aio rt activation list` from the same directory and compare the environment with `dist/.env.local` and the workaround `.env` file. Trace how local credentials are supplied to Runtime commands; done means the command reports the local guest namespace without manually copying or editing environment files.

Written by the indexing model from the issue text.