APIs to support Terminal integration

[sourishkrout]

First stab at providing a session fork/rollup terminal. To make this work following provisional changes were necessary:

1. Beta subcommand to source the current state of the environment, i.e. eval $(runme beta env source...) - similar to how eval $(ssh-agent) works.
2. Subcommand hits gRPC directly, will likely want to move this to an abstraction later.
3. Had to silent some of the autoconf errors since it currently relies on the presence of runme.yaml - will walk this back as part of building out runme beta cmds & autoconf. However, don't want to hold up Runme Terminal progress.
4. Inserted leading spaces into the trap mechanism to skip shell history.

[sourishkrout]

Please review @adambabik. The beta sub cmds are provisional to enable the integration. We'll clean this up as part of a consolidated effort to build out the remaining CLI gap.

[sourishkrout]

Also, any idea why TestTerminalCommand_EnvPropagation is so flakey?

[adambabik]

I added a few comments but no blockers.

[adambabik]

Also, any idea why TestTerminalCommand_EnvPropagation is so flakey?

It relies on the output of bash, but looking at the stack trace in the CI, it seems that _, err = stdinW.Write([]byte{0x04}) // EOT does not necessarily works as expected. Maybe you can try to replace it with _, err = stdinW.Write([]byte("exit\n")). This might be more reliable than sending a signal via stdin.

On macOS it seems fine:

go test -count=5 -timeout 10s -run ^TestTerminalCommand_EnvPropagation$ github.com/stateful/runme/v3/internal/command

[sourishkrout]

On macOS it seems fine:

go test -count=5 -timeout 10s -run ^TestTerminalCommand_EnvPropagation$ github.com/stateful/runme/v3/internal/command

Yep, it runs pretty reliable on macOS but does the inverse on Linux/CI

[sonarcloud]

Quality Gate failed

Failed conditions
8.7% Duplication on New Code (required ≤ 5%)

See analysis details on SonarCloud

[adambabik]

On macOS it seems fine:

go test -count=5 -timeout 10s -run ^TestTerminalCommand_EnvPropagation$ github.com/stateful/runme/v3/internal/command

Yep, it runs pretty reliable on macOS but does the inverse on Linux/CI

I tried to replicate it in a Docker container and it seems much more stable after this change. Usually it's a good indicator for running in the CI. Let's keep an eye on it.