ecs: EcsOptimizedImage ignores additionalCacheKey

### Describe the bug

The static methods of `EcsOptimizedImage` pass `options.cachedInContext` on to the constructor alone, ignoring `options.additionalCacheKey` even though the `EcsOptimizedImageOptions` type has a `additionalCacheKey` key. Since the constructor is private, there is no way to use `EcsOptimizedImage` with `additionalCacheKey`.

### Regression Issue

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

### Last Known Working CDK Library Version

_No response_

### Expected Behavior

Providing `additionalCacheKey` leads to the provided key being included in the key for caching the image ami in cdk context.

### Current Behavior

`additionalCacheKey` is entirely ignored

### Reproduction Steps

construct and use a `new aws_ecs.EcsOptimisedImage.amazonLinux2023(aws_ecs.AmiHardwareType.ARM, { cachedInContext: true, additionaCacheKey: 'cache-key'})`

### Possible Solution

Add `additionalCacheKey: context.additionalCacheKey,` to the constructor arguments in every static method defined in `EcsOptimizedImage`.

### Additional Information/Context

_No response_

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

aws-cdk-lib@npm:2.213.0

### AWS CDK CLI version

2.1027.0 (build 5fc1b13)

### Node.js Version

v22.18.0

### OS

arch linux

### Language

TypeScript

### Language Version

_No response_

### Other information

_No response_

Locate the EcsOptimizedImage class and inspect its private constructor plus each static factory method. Verify how cachedInContext and additionalCacheKey are passed into the image AMI cache key, then add or update coverage so the supplied additionalCacheKey is included.

Written by the indexing model from the issue text.