Atmos terraform shell Prompt Regression

[RoseSecurity]

Describe the Bug

After upgrading from Atmos 1.98.0 to 1.105.0, atmos terraform shell inside of Geodesic does not behavior as expected, producing the following output:

 √ . [devops] (HOST) infra ⨠ atmos terraform shell <component>-s <stack>

Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing modules...

Initializing provider plugins...
- terraform.io/builtin/terraform is built in to Terraform

Terraform has been successfully initialized!

root@e36b6d3f0c3a:/localhost/infra/components/terraform/eks/cluster#

Expected Behavior

The prompt should be maintained as follows:

Terraform has been successfully initialized!
 √ : [devops] (HOST) eks/cluster ⨠ 

Steps to Reproduce

Version:

 √ . [devops] (HOST) infra ⨠ atmos version

👽 Atmos 1.105.0 on linux/arm64

Command:

atmos terraform shell <component> -s <stack>

Screenshots

No response

Environment

No response

Additional Context

No response

[osterman]

Relates to #761

[osterman]

We will get this fixed ASAP. Problem we tried to solve is for non geodesic users the sub shell behavior is not as polished. I think the quick fix is to make this configurable and disabled by default until we have a better working compromise.

[RoseSecurity]

We will get this fixed ASAP. Problem we tried to solve is for non geodesic users the sub shell behavior is not as polished. I think the quick fix is to make this configurable and disabled by default until we have a better working compromise.

I am a big fan of the feature, and haven't read the code for it yet, but if this toggles a environment variable, maybe it could also be accomplished at the Geodesic layer