local.env not used in RODEO correctly

The local.env file uses in non-fully containerized RODEO deploys is not used in the container. This is inconsistent behavior with how local.env is usually used, as it is mounted into /src/local.env.

The solution is not quite as simple as "just mount it into /src/local.env" as the deploy docker might have a local.env for deploy purposes.

So the right answer would be to mount it in somewhere, and use both local.env, using the host local.env first or second? First would be easier, but local.env's don't typically used the :${FOO=bar} pattern, so second takes precedence. We could just say that in the case of RODEO local.env, it should use :${f=b} notation

Start by locating the non-fully-containerized RODEO deploy path and its Docker configuration, then inspect how the host and deploy local.env files are mounted and read. The work is done when the host local.env is available in the container without breaking deploy-specific settings, with a defined precedence between both files.