Feature: Expand envrionment variables on secrets

[veimox]

Why

Better developer experience

What

Nx expands environment variables by default when placed in the project.json. For example,

{
...
"publish": {
      "executor": "@nx-tools/nx-container:build",
      "options": {
        ...
        "build-args": [
          "NPM_TOKEN=${NPM_TOKEN}"
        ],
        ...
      }
    },
...
}

will successfuly pass the argument to the image with the expanded value of the environment variable NPM_TOKEN. However

{
...
"publish": {
      "executor": "@nx-tools/nx-container:build",
      "options": {
        ...
        "secrets": [
          "NPM_TOKEN=${NPM_TOKEN}"
        ],
        ...
      }
    },
...
}

will not. This is because the code right now uses that literal string.

This PR expands the environment variables to provide the implicit developer experience. It will likely takcle issues like #595 where people seem confused regarding this feature. Today we provide examples on how to do this, but only works on CI where value is passed already expanded with the INPUT_ env var like in #650

How

Adds a small function to expand the vars and makes use of it both in dockerx and podman

[gperdomor]

Hi @veimox, thank you for this MR...

Only one request 😄 ...

@nx-tools/core already have an interpolate function to handle this cases... please use that function instead expandEnvVars

[veimox]

Thanks for the tip @gperdomor, I didn't know of it! I just updated it

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit b1c52ae. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 4 targets

• nx affected --target=test --parallel=3 --ci --code-coverage
• nx affected --target=build --parallel=3
• nx affected --target=lint --parallel=3
• nx-cloud record -- npx nx format:check

---

Sent with 💌 from NxCloud.