docs(eks-v2-alpha): remove spot instance related documentation (#34384)

### Issue # (if applicable)

None

### Reason for this change

[spot interrupt handler is installed by default in aws-eks](https://github.com/aws/aws-cdk/blob/393919f760a9257886536e37596dbac6119a9acc/packages/aws-cdk-lib/aws-eks/lib/cluster.ts#L1178-L1182), but not in eks-v2-alpha.



### Description of changes

Remove spot instance related documentation in eks-v2-alpha.



### Describe any new or updated permissions being added




### Description of how you validated changes


This is a documentation-only change. No test modifications are required.

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

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

Author: wafuwafu13

packages/@aws-cdk/aws-eks-v2-alpha/lib/cluster.ts

@@ -177,12 +177,6 @@ export interface ICluster extends IResource, ec2.IConnectable {
    * add the right policies to the instance role, apply the right tags, and add
    * the required user data to the instance's launch configuration.
    *
-   * Spot instances will be labeled `lifecycle=Ec2Spot` and tainted with `PreferNoSchedule`.
-   * If kubectl is enabled, the
-   * [spot interrupt handler](https://github.com/awslabs/ec2-spot-labs/tree/master/ec2-spot-eks-solution/spot-termination-handler)
-   * daemon will be installed on all spot instances to handle
-   * [EC2 Spot Instance Termination Notices](https://aws.amazon.com/blogs/aws/new-ec2-spot-instance-termination-notices/).
-   *
    * Prefer to use `addAutoScalingGroupCapacity` if possible.
    *
    * @see https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html
@@ -811,12 +805,6 @@ abstract class ClusterBase extends Resource implements ICluster {
    * add the right policies to the instance role, apply the right tags, and add
    * the required user data to the instance's launch configuration.
    *
-   * Spot instances will be labeled `lifecycle=Ec2Spot` and tainted with `PreferNoSchedule`.
-   * If kubectl is enabled, the
-   * [spot interrupt handler](https://github.com/awslabs/ec2-spot-labs/tree/master/ec2-spot-eks-solution/spot-termination-handler)
-   * daemon will be installed on all spot instances to handle
-   * [EC2 Spot Instance Termination Notices](https://aws.amazon.com/blogs/aws/new-ec2-spot-instance-termination-notices/).
-   *
    * Prefer to use `addAutoScalingGroupCapacity` if possible.
    *
    * @see https://docs.aws.amazon.com/eks/latest/userguide/launch-workers.html
@@ -1428,10 +1416,6 @@ export class Cluster extends ClusterBase {
    * time without notice in case the recommended AMI for your machine image type has been updated by AWS.
    * The default behavior for `updateType` is `None`, which means only new instances will be launched using the new AMI.
    *
-   * Spot instances will be labeled `lifecycle=Ec2Spot` and tainted with `PreferNoSchedule`.
-   * In addition, the [spot interrupt handler](https://github.com/awslabs/ec2-spot-labs/tree/master/ec2-spot-eks-solution/spot-termination-handler)
-   * daemon will be installed on all spot instances to handle
-   * [EC2 Spot Instance Termination Notices](https://aws.amazon.com/blogs/aws/new-ec2-spot-instance-termination-notices/).
    */
   @MethodMetadata()
   public addAutoScalingGroupCapacity(id: string, options: AutoScalingGroupCapacityOptions): autoscaling.AutoScalingGroup {