eks.albController: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress

### Describe the bug

I am struggling to create an EKS cluster with an ALB Controller installed. I have tried a few variations of configuration based on related issues opened in the past but all of them lead to the same underlying Helm error `UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress`. Related issues and other things I've tried are linked in the below sections.

I'm currently unsure if this is strictly a bug or just a miss in documentation explaining how the properly set up ALB Controllers.

### Regression Issue

- [ ] Select this option if this issue appears to be a regression.

### Last Known Working CDK Library Version

_No response_

### Expected Behavior

ALB Controller is properly installed on the cluster.

### Current Behavior

Helm errors trying to install the ALB Controller with `UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress`.

### Reproduction Steps

```ts
const vpc = new Vpc(this, "Vpc");

const eksCluster = new Cluster(this, "EKSCluster", {
clusterName: props.resourcePrefix,
defaultCapacity: 0,
kubectlLayer: new KubectlV34Layer(this, "EKSKubectlLayer"),
placeClusterHandlerInVpc: true,
version: KubernetesVersion.V1_34,
vpc,
vpcSubnets: [{ subnetType: SubnetType.PRIVATE_WITH_EGRESS }],
});

const eksNodegroup = eksCluster.addNodegroupCapacity("EKSNodegroup", {
amiType: NodegroupAmiType.AL2023_X86_64_STANDARD,
desiredSize: 2,
enableNodeAutoRepair: true,
instanceTypes: [InstanceType.of(InstanceClass.M5, InstanceSize.LARGE)],
nodegroupName: `${props.resourcePrefix}-nodegroup-m5-large`,
});

const eksAlbController = new AlbController(this, "EKSAlbController", {
cluster: eksCluster,
version: AlbControllerVersion.V2_8_2,
});
eksAlbController.node.addDependency(eksNodegroup);
```

### Possible Solution

_No response_

### Additional Information/Context

I have found 3 related issues that I've read through and followed the suggestions for:

- https://github.com/aws/aws-cdk/discussions/19705#discussioncomment-7173148
- https://github.com/aws/aws-cdk/issues/22005#issuecomment-1861893693
- https://github.com/aws/aws-cdk/issues/27641

Adding a default capacity, creating manual dependencies for the ALB controller to wait for node groups to be ready, increasing the size of node group, and creating the cluster first in a separate deploy all did not resolve the issue for me.

### AWS CDK Library version (aws-cdk-lib)

2.240.0

### AWS CDK CLI version

2.1107.0

### Node.js Version

24.13.1

### OS

macOS Tahoe 26.3 (Apple Silicon)

### Language

TypeScript

### Language Version

5.9.3

### Other information

_No response_

Start with the AlbController entry point and the provided TypeScript reproduction, then review the three linked discussions and issues for the Helm operation error. Verify the cluster, node group, and controller deployment sequence; done means the ALB Controller installs successfully without the concurrent-operation failure.

Written by the indexing model from the issue text.