chore: migrate @aws-cdk-testing/cli-integ from sdk v2 to sdk v3

[vinayak-kukreja]

Closes #29837

Reason for this change

We are migrating our code from SDK v2 to SDK v3. This change is part of that effort.

Description of changes

We used to have an abstracted caller since SDK v2 did not have separated clients. Since SDK v3 now have separated clients, I am also making code changes to reflect that and not moving forwards with the abstracted client vendor.

Also, updated the imports and references to work with SDK v3 and introduced ini for reading aws config files, since SDK v3 changed the functionality from sync to async and to add that to our code would mean a lot more of changes for adding a simple functionality

Description of how you validated changes

The run through test pipeline is successful.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

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

[vinayak-kukreja]

This is really weird. If we mention 3.421.0 it leads to test errors in packages/@aws-cdk/custom-resource-handlers/test/aws-events-targets/aws-api-handler/aws-api-handler.test.ts. Unfortunately, we had set the client version to 3.451.0 in there.

I see there is a lot of mismatch between sdk versions in different package.jsons and we need to align them to same version. We cannot lower them to a previous version, so probably will end up aligning to the version that is the highest in our package.

[vinayak-kukreja]

I see some integ tests not running since they are unable to find credentials:

  ● update to stack in ROLLBACK_COMPLETE state will delete stack and create a new one
    Profile 'long-running-profile' does not exist in config file (/root/.aws/config)
      at chainableCredentials (../../lib/aws.ts:231:13)
      at new chainableCredentials (../../lib/aws.ts:39:20)
      at Function.forRegion (../../lib/aws.ts:21:12)
      at forRegion (../../lib/with-aws.ts:18:34)
      at ResourcePool.block (../../lib/resource-pool.ts:72:20)
      at ../../lib/integ-test.ts:51:14

This is due to a different path for config defined in delivlib here. Taking a look into how this binds with our test infrastructure.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 7f7b528
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[aws-cdk-automation]

➡️ PR build request submitted to test-main-pipeline ⬅️

A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

[bergjaak]

should we be throwing an error here? I don't see that we did this before... I'm wondering if throwing here would cause resources to leak in the case that this error is thrown?

[bergjaak]

Similar comment as my above comment. Why add the behavior of throwing error?