feat: expand env variable by default

[wingyplus]

Fixes #7171

The withEnvVariable API will expand shell env variable by default. And
add noExpand option to do not expand when it's set to true. The
expand option is now deprecated but still compatible with the previous
version.

[wingyplus]

Just open a PR to see what you thought. If you're all agree, I can put this work forward. :)

[wingyplus]

I hit an issue on Go SDK now. When I change Expand default in GraphQL api to true. The no expand variable test get failure:

=== NAME  TestContainerWithEnvVariableExpand/add_env_var_without_expansion
    container_test.go:1080: 
                Error Trace:    /home/wingyplus/src/github.com/dagger/dagger/core/integration/contain
                Error:          Not equal: 
                                expected: "foo:$PATH\n"
                                actual  : "foo:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbi
                            
                                Diff:
                                --- Expected
                                +++ Actual
                                @@ -1,2 +1,2 @@
                                -foo:$PATH
                                +foo:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
                                 
                Test:           TestContainerWithEnvVariableExpand/add_env_var_without_expansion

After digging into an issue. The WithEnvVarible Go SDK api detect optional argument by IsZero, cause boolean value not set to query when Expand is false.

If I understand it correctly, we need to modify the codegen to always pass the boolean value. Or we have another way to fix this?

[helderco]

If I understand it correctly, we need to modify the codegen to always pass the boolean value. Or we have another way to fix this?

Yeah, I guess we've always avoided this. Even in #7136, the way to flip the default on skipEntrypoint is to deprecate it in favor of a new useEntrypoint.

To do the same here we'd need a new option like noExpand that defaults to false. It also helps with the deprecation because you can detect if someone is using the older expand or not.

[wingyplus]

@helderco I just add noExpand option as you suggested. I'm not sure how to do with expand so I make it compatible for now. 🙏

[helderco]

Waiting on status of:

• Allow env variable interpolation in Container.withEnvVariable #7171