fix: Parse command output without using shell pipelines

[dlipovetsky]

What problem does this PR solve?:
Errors are not being caught when the shell module executes a pipeline. For example, see #367 (comment)

It's possible to catch errors by using the pipefail shell option, but only if the shell supports it. In every case where we use a pipeline, we use it to parse command output. Instead of catching errors, we can just stop using pipelines.

Which issue(s) does this PR fix?:

• https://jira.d2iq.com/browse/D2IQ-NUMBER

Special notes for your reviewer:

The e2e tests fail, as expected. They will pass once #367 is merged. Merged.

Does this PR introduce a user-facing change?:

[github-actions]

File	Coverage
All files	16%	❌
pkg/ansible/runner.go	0%	❌
pkg/app/artifacts.go	0%	❌
pkg/app/build.go	1%	❌
pkg/app/build_azure.go	0%	❌
pkg/app/build_gcp.go	0%	❌
pkg/app/config.go	47%	❌
pkg/app/errors.go	0%	❌
pkg/app/provision.go	0%	❌
pkg/app/root.go	0%	❌
pkg/app/validate.go	0%	❌
pkg/appansible/io.go	0%	❌
pkg/appansible/playbook.go	0%	❌
pkg/azure/azure.go	0%	❌
pkg/logging/logger.go	0%	❌
pkg/packer/manifest.go	0%	❌
pkg/packer/packer.go	0%	❌
pkg/stringutil/rand.go	0%	❌
pkg/version/info.go	8%	❌

Minimum allowed coverage is 75%

Generated by 🐒 cobertura-action against d7467a1

[dlipovetsky]

After #367 merged, I rebased on main and force-pushed. The e2e tests should now pass.

[dkoshkin]

Thanks for fixing all tasks

[dlipovetsky]

Ubuntu 18.04 and 20.04 tests are failing apparently because /bin/sh is not bash, and set -o pipefail is unrecognized. Will fix.

[dlipovetsky]

Ubuntu 18.04 and 20.04 tests are failing apparently because /bin/sh is not bash, and set -o pipefail is unrecognized. Will fix.

I tried to fix this by relying on /usr/bin/env bash, but that proved tricky to do. So instead I went all-in on the "native" parsing approach introduced recently by @faiq.

[dlipovetsky]

Sadly and unexpectedly, the cli_parse module didn't work for my needs, and its errors were inscrutable. So I went with regex parsing.