feat: optionally hide multienv output

[anryko]

what

Add a "full" configuration type for the multienv workflow step type identical to the run step type, to allow users to silence the output.

why

• The multienv can contain a long list of variables that trashes the output.
• Exported variable names might be security-sensitive.

tests

• I have tested my changes by providing additional tests in the code and manually by passing the following repo config variable in my dev env.

ATLANTIS_REPO_CONFIG_JSON='
{
  "repos": [
    {
      "id": "/.*/",
      "apply_requirements": [
        "mergeable"
      ],
      "allowed_overrides": [
        "apply_requirements",
        "workflow"
      ],
      "allow_custom_workflows": true,
      "pre_workflow_hooks": [
        {
          "run": "echo \"HI IAM DEV INSTANCE\""
        }
      ]
    }
  ],
  "workflows": {
    "custom": {
      "plan": {
        "steps": [
          {
            "run": "echo \"PLAN THE STEP 1\""
          },
          {
            "multienv": {
                "command": "/atlantis/src/multienv_test.sh",
                "output": "hide"
            }
          },
          {
            "run": "echo \"PLAN THE STEP 2\""
          },
          {
            "multienv": {
                "command": "/atlantis/src/multienv_test.sh",
                "output": "show"
            }
          },
          {
            "run": "echo \"PLAN THE STEP 3\""
          },
          {
            "multienv": {
                "command": "/atlantis/src/multienv_test.sh"
            }
          },
          {
            "run": "echo \"PLAN THE STEP 4\""
          },
          {
            "multienv": "/atlantis/src/multienv_test.sh"
          }
        ]
      }
    }
  }
}'

references

• closes toggle to silence multienv output #4388

[Gabidiela]

Hi, do we have any plans for this solution to be implemented? I have a problem and I think this would help a lot.

[chenrui333]

not quite sure why e2e tests run on the merge commit