feat(stepfunctions-tasks): start build batch integration

[badmintoncryer]

Issue # (if applicable)

Closes #29119.

Reason for this change

There is an optimized integration with codebuild but it is not able to integrate by AWS CDK.

Description of changes

Add CodeBuildStartBuildBatch class

declare const project: codebuild.Project;

const buildconfig = project.enableBatchBuilds();

const startBuildBatch = new tasks.CodeBuildStartBuildBatch(this, 'buildTask', {
      project,
      integrationPattern: sfn.IntegrationPattern.REQUEST_RESPONSE,
      environmentVariablesOverride: {
        test: {
          type: codebuild.BuildEnvironmentVariableType.PLAINTEXT,
          value: 'testValue',
        },
      },
});

Description of how you validated changes

I've implemented both unit and integ tests.

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

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[lpizzinidev]

Looks good 👍
I left some suggestions for cleaning up the documentation.

[badmintoncryer]

@lpizzinidev Thank you for your review!! I've addressed your comment.

[lpizzinidev]

Can you please add a note below explaining the scenarios when enableBatchBuilds() returns undefined?
Eg:

**Note**: Batch builds are not supported for ... 

You can verify if batch builds are enabled by checking `enableBatchBuilds()` returned value:

```ts
const enabled = project.enableBatchBuilds();
if (enabled === undefined) {
  throw new Error('Batch build were not enabled');
}

[badmintoncryer]

@lpizzinidev

I have added only Notes.

The enableBatchBuilds() returns undefined exclusively for imported projects, and this return value persists regardless of the batch build's actual status (enabled or not) within those projects. Consequently, users working with imported projects must manually ensure that batch builds are enabled, as relying on the return value of enableBatchBuilds() is not informative.

I believe it suffices to include this as a note without detailing the process of verifying the return value of enableBatchBuilds().
What do you think about that?
I'm sorry for my initial README desciption confused you...

[lpizzinidev]

Thanks for the detailed clarification 👍

[badmintoncryer]

@lpizzinidev Thanks!!

[GavinZZ]

Thanks @badmintoncryer for the PR and @lpizzinidev for the detailed review. The changes look good. Happy to approve it.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

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

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

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).