test: add integration tests for CLI client

[reedham-aws]

Integration test PR for buildkit/container CLI support.

Added a few parameterized tests for some image based tests, as well as just general tests for using the --use-buildkit flag. Worth noting is that when using the CLI, there were a lot of resource warnings that the sockets were being left open. I couldn't figure out a fix to this, but I think they're harmless warnings so I ignored them.

Implementation PR: #8661.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[roger-zhangg]

prob need to merge from develop for the chardet thing

[roger-zhangg]

would suggest to add a ARM64 test, and then mark one test -> x86/arm64 as https://github.com/aws/aws-sam-cli/blob/develop/CONTRIBUTING.md#tier-1-cross-platform-smoke-tests for running that test on finch / windows (to be added)

[reedham-aws]

would suggest to add a ARM64 test, and then mark one test -> x86/arm64 as https://github.com/aws/aws-sam-cli/blob/develop/CONTRIBUTING.md#tier-1-cross-platform-smoke-tests for running that test on finch / windows (to be added)

Done, I added as tier1, although not sure if this would have fallen more into the tier1_extra category. I think the testing of the CLI is important enough, not sure about the parameters.

[reedham-aws]

Integ test run: https://github.com/aws/aws-sam-cli/actions/runs/22508505787

[vicheey]

Will there be change in VS Code extension for this feature? If so, should we have a negate version of this as well: --no-use-buildkit. This should be similar to

aws-sam-cli/samcli/commands/_utils/options.py

Line 852 in c95e0ac

"--use-container/--no-use-container",

[reedham-aws]

--no-use-buildkit exists in the implementation, is it required to be in the test options as well?

[reedham-aws]

Latest integration test run: https://github.com/aws/aws-sam-cli/actions/runs/22595806682. I removed the ARM64 test because it wasn't working well in x86 environment. While BuildKit should technically support this, that's more testing a BuildKit feature than our implementation. I think QEMU needs to be set up in some way in the environment for it to fully work.

Edit: All related and non-flaky tests are passing

[reedham-aws]

Latest test run: https://github.com/aws/aws-sam-cli/actions/runs/22649580848

Before, the tier1-finch tests were failing. This is because the test was incorrectly finding that the finch CLI was unavailable. The problem was that in the CI runner, finch required sudo to run, but the code did not supply it. The solution was to make it so that sudo was not required for finch or nerdctl.

sudo chmod +s "$NERDCTL_PATH"
sudo chmod +s /usr/bin/finch